Mobile app development is a fast moving target. You have many options on how to develop mobile apps.
The most sophisticated way is to write native apps for each platform...
Of course you will need to master the different languages and development environments. And since you will have to develop the same functionality for several platforms, you will code it multiple times in different languages.
Happy you if you find a customer willing to pay for it.
If you wish to use the "write once run anywhere" system, then you will be landing on web apps. Fortunally today mobile devices are in most cases fast enough to run you web app without feeling slugish. So you basically can write a html 5 website and make it available as a app.
For this you can use the phonegap / cordova framework.
If you need access to some native parts of the mobile device (Sensors, camera etc.) then you can use many of the available plugins which then allows you to access these hardware specific features.
Even better, you can use the adobe build service to build the whole application from your html/javascript sources.
If you come from the java world, then writing javascript isn't that sexy, you could then use GWT to write your web app in java and let the compiler generate java script stuff from it.
The performance of the generated code is very good, you will have a hard time to make such optimized java script code.
In this blog post serie I will guide you through the process of creating a project in netbeans, which you can then use to build your mobile application from your familiar ide.
Such apps are able to run under iOS, Android and Windows Phone. Of course platform specific features will only be available on the specific platform.
So let's start with Part 1 of the tutorial
Step 2 - Modify content
Step 3 - Build native apps
Monday, June 2, 2014
Friday, February 21, 2014
Installing the DHCP Role on Windows 2012 R2 Server
Unable to install DHCP server role on Windows 2012 Server Essential.
When you try to install the DHCP Role on a windows 2012 R2 server, then the role installation might just stop with the error "0x800f0922".
Searching for this error message shows a astonishing amount of questions about this, so you are in good company.
Some solutions tell you to disable automatic web proxy detection, or disconnect the network cable from the server during the installation of the DHCP role.
When you wish to know what happens, then look in the %SYSTEMROOT%\System32\DHCP for some logfiles.
In our case the newly installing dhcp server detects a already running dhcp server in the network and so refuses to install a local DHCP server.
So it's clear why disconnecting the network cable solves the installation problem, the other dhcp server is then no longer visible.
But why, why is preventing the installation of the dhcp server role?
And why, why is there such a cryptic nonsense error message instead of a real error message?
When you try to install the DHCP Role on a windows 2012 R2 server, then the role installation might just stop with the error "0x800f0922".
Searching for this error message shows a astonishing amount of questions about this, so you are in good company.
Some solutions tell you to disable automatic web proxy detection, or disconnect the network cable from the server during the installation of the DHCP role.
When you wish to know what happens, then look in the %SYSTEMROOT%\System32\DHCP for some logfiles.
In our case the newly installing dhcp server detects a already running dhcp server in the network and so refuses to install a local DHCP server.
So it's clear why disconnecting the network cable solves the installation problem, the other dhcp server is then no longer visible.
But why, why is preventing the installation of the dhcp server role?
And why, why is there such a cryptic nonsense error message instead of a real error message?
Labels:
dhcp,
setup,
windows 2012R2,
windows 2012r2 essentials
Wednesday, February 19, 2014
Adding a Windows 2012 R2 Essential Server to a existing domain
Adding a new Windows 2012 R2 Essentials server to a existing domain is a supported scenario by microsoft.
The new server will then be the primary server for all the ADS roles.
Unfortunally this does not mean it will just work out of the box.
The basic steps for this are:
- Make the basic installtion of the windows server
- Don't follow the wizard after installation, just cancel it
- Important: Set the server name you wish to use now, you won't be able to change it later on
- Install the Active Directory Services on the new server
- Add the new server as a additional ADS server in the existing domain
- Let the wizard finish the essentials configuration
The details can be found on the microsoft product site.
Unfortunally the wizard won't finish, but rather say: Error occured and nothing is logged.
The post-config wizard won't let you configure the Essentials Experience role because it's unable to start the 'Windows Server Essentials Management Service' system service. This service is configured to run under the <domain>\ServerAdmin$ account. This account must have 'Log on as a service' rights.
The new server will then be the primary server for all the ADS roles.
Unfortunally this does not mean it will just work out of the box.
The basic steps for this are:
- Make the basic installtion of the windows server
- Don't follow the wizard after installation, just cancel it
- Important: Set the server name you wish to use now, you won't be able to change it later on
- Install the Active Directory Services on the new server
- Add the new server as a additional ADS server in the existing domain
- Let the wizard finish the essentials configuration
The details can be found on the microsoft product site.
Unfortunally the wizard won't finish, but rather say: Error occured and nothing is logged.
The post-config wizard won't let you configure the Essentials Experience role because it's unable to start the 'Windows Server Essentials Management Service' system service. This service is configured to run under the <domain>\ServerAdmin$ account. This account must have 'Log on as a service' rights.
- Go to Group Policy Management
- Edit your policy, such as the 'Default Domain Controllers Policy'
- Go to Computer Configuration \ Windows Settings \ Security Settings \ Local Policies \ User Rights Assignment
- Edit 'Log on as a service' and add 2 accounts: <domain>\ServerAdmin$ and <domain>\MediaAdmin$
Labels:
ads,
windows,
windows 2012R2,
windows 2012r2 essentials
Thursday, January 23, 2014
Vaadin JPAContainer, Filterable table and related entities
In the web 2.0 framework Vaadin you have containers which provide data to be displayed in your application.
These containers are very flexible and can for example be a databasebackend, a JPA system or your own implementation.
In my past post I showed you how to implement filtering for related fields.
Vaadin also provides many data aware components, for example a table component.
The table component is very sophisticated and allows displaying huge amounts of data in the webbrowser. The table has a lazy loading system, so as only the visible parts of a table are retrieved from the backend and sent to the webbrowser.
There also exists a addon component which has built in filter and sort support.
When using the table with jpa container, then you have to use several tricks to allow filtering on related fields.
You don't have to store the property, it's enough for the JPA container when you have a getXXX() method.
That way it displays the additional properties in the table. You could also use this way to show calculated related fields in the table.
This could look like this:
public String getProjectInfos()
{
return projectNr+" - "+name;
}
When you now display these in the table, you can also filter on that field.
But then, you will get a error message, telling you that the sql select did not find the field for the where condition.
contentTable.setFilterGenerator(new MyFilterGenerator());
The filter generator has different methods, when you don't want to override them, you can just return NULL and then the default behaviour is done.
For us the interesting method is the generateFilter() method.
Here you can implement your own conditions.
If you for example wish to filter with the LIKE statement, then you can do it this way:
@Override
public Container.Filter generateFilter(Object propertyId, Object value)
{
if ("contract".equals(propertyId))
{
if (value != null && value instanceof String)
{
return new Like("contractID", value.toString()+"%");
}
}
return null;
}
To now filter on a related table, you can use the IN condition, which then builds the correct sql statements.
@Override
public Container.Filter generateFilter(Object propertyId, Object value)
{
if ("contracts".equals(propertyId))
{
if (value != null && value instanceof String)
{
String lsNr= (String) value;
EntityManager em= ((MyVaadinUI)UI.getCurrent()).getEntityManager();
TypedQuery<Shippings> tq= em.createNamedQuery("Shippings.findByLikeProjectNr", Shippings.class);
tq.setParameter("projectNr", lsNr+"%");
List<Shippings> rs= tq.getResultList();
if (rs.isEmpty())
{
return new IsNull("shipping");
}
else
{
if (rs.size() > 2000)
{
Notification.show("To many entries", "\n\nMake more restrictions", Notification.Type.WARNING_MESSAGE);
return new IsNull("shipping");
}
else
{
return new In("shipping", rs);
}
}
}
}
return null;
}
So when the property contracts has some value, we filter the contracts by projectNr and use the resulting result set to specify as the IN criteria.
If you are still with me, then you probably have a compiler error when you try this code.
The reason is, that the default JPAContainer has no implementation of the IN criteria.
Unfortunally the design of the JPAContainer does not allow to expand the capabilities in that area.
Fortunally there exists a fork of the JPAContainer which just provides the required IN() clause.
You can download the sources and add them to your project.
The source can be found here: https://github.com/lelmarir/jpacontainer
You can learn how to show related / nested properties in this post.
These containers are very flexible and can for example be a databasebackend, a JPA system or your own implementation.
In my past post I showed you how to implement filtering for related fields.
Vaadin also provides many data aware components, for example a table component.
The table component is very sophisticated and allows displaying huge amounts of data in the webbrowser. The table has a lazy loading system, so as only the visible parts of a table are retrieved from the backend and sent to the webbrowser.
There also exists a addon component which has built in filter and sort support.
When using the table with jpa container, then you have to use several tricks to allow filtering on related fields.
The first trick is to display the related fields in the table
For this the simplest way is to add these related fields to the main entity you display.You don't have to store the property, it's enough for the JPA container when you have a getXXX() method.
That way it displays the additional properties in the table. You could also use this way to show calculated related fields in the table.
This could look like this:
public String getProjectInfos()
{
return projectNr+" - "+name;
}
When you now display these in the table, you can also filter on that field.
But then, you will get a error message, telling you that the sql select did not find the field for the where condition.
For this to work, you have to use the second trick
You can build your own FilterGenerator which then builds the correct criterias for your tables and relations.contentTable.setFilterGenerator(new MyFilterGenerator());
The filter generator has different methods, when you don't want to override them, you can just return NULL and then the default behaviour is done.
For us the interesting method is the generateFilter() method.
Here you can implement your own conditions.
If you for example wish to filter with the LIKE statement, then you can do it this way:
@Override
public Container.Filter generateFilter(Object propertyId, Object value)
{
if ("contract".equals(propertyId))
{
if (value != null && value instanceof String)
{
return new Like("contractID", value.toString()+"%");
}
}
return null;
}
To now filter on a related table, you can use the IN condition, which then builds the correct sql statements.
@Override
public Container.Filter generateFilter(Object propertyId, Object value)
{
if ("contracts".equals(propertyId))
{
if (value != null && value instanceof String)
{
String lsNr= (String) value;
EntityManager em= ((MyVaadinUI)UI.getCurrent()).getEntityManager();
TypedQuery<Shippings> tq= em.createNamedQuery("Shippings.findByLikeProjectNr", Shippings.class);
tq.setParameter("projectNr", lsNr+"%");
List<Shippings> rs= tq.getResultList();
if (rs.isEmpty())
{
return new IsNull("shipping");
}
else
{
if (rs.size() > 2000)
{
Notification.show("To many entries", "\n\nMake more restrictions", Notification.Type.WARNING_MESSAGE);
return new IsNull("shipping");
}
else
{
return new In("shipping", rs);
}
}
}
}
return null;
}
So when the property contracts has some value, we filter the contracts by projectNr and use the resulting result set to specify as the IN criteria.
If you are still with me, then you probably have a compiler error when you try this code.
The reason is, that the default JPAContainer has no implementation of the IN criteria.
Unfortunally the design of the JPAContainer does not allow to expand the capabilities in that area.
Fortunally there exists a fork of the JPAContainer which just provides the required IN() clause.
You can download the sources and add them to your project.
The source can be found here: https://github.com/lelmarir/jpacontainer
You can learn how to show related / nested properties in this post.
Labels:
container,
filteringtable,
java,
jpa,
jpacontainer,
vaadin
Run linux commands via job queue
Often we have build long running jobs under linux which then call other shell scripts when they are finished.
Sometimes it would be possible to run such tasks partially concurrently, but for this we need some sort of job queue for the linux shell.
Unfortunally the cron/crontab does not allow such dependencies.
The simplest solution is to install the task spooler from this site.
You should however first look if your distribution has a binary package for it.
In debian you can install it via:
apt-get install task-spooler
After this, you can just put new jobs in the queue via the ts command.
Please note that in debian the command is named tsp to prevent name conflicts with the moreutils package.
When you just type ts(p) the system shows you all running/pending/completed tasks.
To put a new job in the queue you just type this:
ts(p) /home/user/mytask.sh
The job is then startet as soon as possible.
Per default the task spooler does start one task and waits until it is finished.
When the first task is finished it executes the next one from the queue and so on, until the queue is empty.
You can tell the task spooler to run multiple tasks concurrently,
you just set the maximum number of allowed concurrent executions with this command:
ts(p) -S 2
This would allow the task spooler to run up to two tasks concurrently.
You can also set priority on tasks, remove them from the queue an so on.
Look at the man page for more details.
As of 0.7.3 the man page does not list all options, to see all available options, use the -h option.
The output of the jost is per default stored in files in the /tmp folder.
You can view them, or use ts(p) to send them via email to some destination.
Sometimes it would be possible to run such tasks partially concurrently, but for this we need some sort of job queue for the linux shell.
Unfortunally the cron/crontab does not allow such dependencies.
The simplest solution is to install the task spooler from this site.
You should however first look if your distribution has a binary package for it.
In debian you can install it via:
apt-get install task-spooler
After this, you can just put new jobs in the queue via the ts command.
Please note that in debian the command is named tsp to prevent name conflicts with the moreutils package.
When you just type ts(p) the system shows you all running/pending/completed tasks.
To put a new job in the queue you just type this:
ts(p) /home/user/mytask.sh
The job is then startet as soon as possible.
Per default the task spooler does start one task and waits until it is finished.
When the first task is finished it executes the next one from the queue and so on, until the queue is empty.
You can tell the task spooler to run multiple tasks concurrently,
you just set the maximum number of allowed concurrent executions with this command:
ts(p) -S 2
This would allow the task spooler to run up to two tasks concurrently.
You can also set priority on tasks, remove them from the queue an so on.
Look at the man page for more details.
As of 0.7.3 the man page does not list all options, to see all available options, use the -h option.
The output of the jost is per default stored in files in the /tmp folder.
You can view them, or use ts(p) to send them via email to some destination.
Wednesday, January 22, 2014
Installing additional skins in CKEditor 4.x
CKEditor is one of the most sophisticated webbrowser base html editors available.
The original version was named fckeditor and going to version 3 it was renamed to be simply ckeditor.
The F in the name was for the first name of the author, Frederico.
When you use the version 4 of the editor, you will receive a new look, due to large changes in the default skin. It is now blackgray/white instead of the "colorful" 3.x version.
A huge improvement in my opinion. The bright colors in 3.x where not looking very professional.
If for some reasons you wish to use another skin, then you can download alternate skins from the ckeditor home page with this link.
When downloading, it tells you how to install and activate the new skin.
Unfortunally this info is mostly wrong, and even in the main documentation the same errors are present.
To successfully install the new skin, you have to put the extracted files in the skins subdirectory (not in the plugins).
And to activate the new skin, you have to specify the config.skin = "new_skin" property. (And not the config.extraPlugin as documented).
So if you wish to have the "old" 3.x icons and colors, you can download the "kama" skin and activate it.
The original version was named fckeditor and going to version 3 it was renamed to be simply ckeditor.
The F in the name was for the first name of the author, Frederico.
When you use the version 4 of the editor, you will receive a new look, due to large changes in the default skin. It is now blackgray/white instead of the "colorful" 3.x version.
A huge improvement in my opinion. The bright colors in 3.x where not looking very professional.
If for some reasons you wish to use another skin, then you can download alternate skins from the ckeditor home page with this link.
When downloading, it tells you how to install and activate the new skin.
Unfortunally this info is mostly wrong, and even in the main documentation the same errors are present.
To successfully install the new skin, you have to put the extracted files in the skins subdirectory (not in the plugins).
And to activate the new skin, you have to specify the config.skin = "new_skin" property. (And not the config.extraPlugin as documented).
So if you wish to have the "old" 3.x icons and colors, you can download the "kama" skin and activate it.
Wednesday, December 4, 2013
Fix orphan users in MS SQL Server after restore
When you restore a MS SQL Server to a different machine, you might expect orphan users.
This also happens when you detach a database and then attach it on another server.
You see the users in the Security->Users section of the sql server and also in the database itself, but you can't login with it.
The problem is, that MS SQL stores the SID along the users, and when you restore it on another MS SQL server the link between user names and SID won't match any longer.
Fixing this via GUI is unfortunally not possible, when you try to map the user it trys to create a new sql user and fails, because there already exists such a user.
Fortunally there are a few stored procedures (available since sql 2000 version) which help you fix the logins.
First, make sure that this is the problem. This will lists the orphaned users:
This also happens when you detach a database and then attach it on another server.
You see the users in the Security->Users section of the sql server and also in the database itself, but you can't login with it.
The problem is, that MS SQL stores the SID along the users, and when you restore it on another MS SQL server the link between user names and SID won't match any longer.
Fixing this via GUI is unfortunally not possible, when you try to map the user it trys to create a new sql user and fails, because there already exists such a user.
Fortunally there are a few stored procedures (available since sql 2000 version) which help you fix the logins.
First, make sure that this is the problem. This will lists the orphaned users:
If you already have a login id and password for this user, fix it by doing:EXEC sp_change_users_login 'Report'
If you want to create a new login id and password for this user, fix it by doing:EXEC sp_change_users_login 'Auto_Fix', 'user'
EXEC sp_change_users_login 'Auto_Fix', 'user', 'login', 'password'
Subscribe to:
Posts (Atom)