Java GUI implementation with Eclipse SWT, Eclipse Visual Editor Project and Maven: Part 1


My team have been assigned to perform the evaluation and POC for the GUI for Client/Server application. Firstly I focus to other tools instead of Java, since I’ve known that writing the Java GUI is a nightmare. On the other hand, if we use the new tools I need to learn it from the beginning, the new tools, new language, new framework and so on. The new tools may be limited to perform for some environment/OS. Then we have agreed and decided to use our well-known, Java.


My objective for searching the tools is as following: –

1. It should be a visual editor, since it will help us to speed up the GUI development.

2. It should support the Maven, since it is our build tool and support the CI integration.

3. There should be a GUI unit testing based on JUnit, since it can be integrated to the Maven for generate the code coverage and code quality analysis.


After a couple days searching via the internet. I’ve found the Eclipse: Visual Editor Project which supports the Java GUI development in 2 frameworks, Swing/JFC and SWT/RCP.

SWT/RCP !!!??? What is it ?

After reading the Eclipse: RCP and Eclipse: SWT, I thought that the Eclipse: RCP is equal to the JFC and the Eclipse: SWT is equal to the Swing. The SWT binary/runtime also provides the supporting to many OS platform, i.e. Windows, Mac, Linux, Solaris, AIX.

I also found the Eclipse: RAP as well. It is a platform which lets we build rich, Ajax-enabled Web applications by using the Eclipse development model, plug-ins with the well known Eclipse workbench extension points and a widget toolkit with SWT API. Existing RCP applications can be run as Web applications with only minor changes. It also provides the single sourcing, use the same code for multiple platform. It is worth enough to learn the single platform development for creating the GUI which can be executed by the Client/Server through the Web based.

Regarding to the unit testing, I found the Eclipse: SWTBot and the further information. It can be integrated to the JUnit and also provides the GUI functional testing, including with the keyboard/keystroke testing.


I’ve a tool for GUI development which provide the binary/runtime which can be executed in many environment/OS and architecture(Client/Server and Web based), including with the unit testing tool which support the JUnit. Especially, all of them support the Maven. In the next post, I will show you the traditional example “Hello World” for SWT/RCP, including with the unit testing. Please stay tuned.

2010 in review

The stats helper monkeys at mulled over how this blog did in 2010, and here’s a high level summary of its overall blog health:

Healthy blog!

The Blog-Health-o-Meter™ reads Fresher than ever.

Crunchy numbers

Featured image

A helper monkey made this abstract painting, inspired by your stats.

A Boeing 747-400 passenger jet can hold 416 passengers. This blog was viewed about 1,900 times in 2010. That’s about 5 full 747s.

In 2010, there were 23 new posts, not bad for the first year!

The busiest day of the year was November 17th with 212 views. The most popular post that day was Java Development with NetBeans and Maven: Part 1.

Where did they come from?

The top referring sites in 2010 were, Google Reader,,, and

Some visitors came searching, mostly for netbeans 6.9.1 maven cannot find package, java.lang.noclassdeffounderror: 6/8ide12modulesextjaxbapi, and keystore location and truststore location netbeans 6.8.

Attractions in 2010

These are the posts and pages that got the most views in 2010.

Java Development with NetBeans and Maven: Part 1 November 2010

Java Development with NetBeans and Maven: Part 2 November 2010

Java Development with NetBeans and Maven: Part 3 November 2010

The EJB 3.1: IIOP/SSL July 2010

Java Development with NetBeans and Maven: Part 5 November 2010

Java Development with NetBeans and Maven: Part 5


I hope we are well prepared for moving further to the very powerful “Maven” features, which we have known before, the “site”, especially the “report” integration to the outer world. There are many powerful “Maven Plug-in” provided by the “Maven” itself. You can see further information here. From now on, I will introduce you the “Reporting Plug-ins”.

The Report Plug-ins

Regarding the “Maven Plug-inhere, you may be noticed that there are two plug in which we used before. Guess what? The “project-info-reports”, the “mvn site” command itself and the “surefire-report”, the testing report for our previous JUnit. You already know how easy it is. The rest plug in also be same for sure. One picture can give us a thousand words. Here is my tested template “Project POM File” (pom.xml). Please feel free to modify it so that it is fit for your environment.

<project xmlns="" xmlns:xsi=""
    <url>The Project web site URL</url>
    <description>The SDLC Learning</description>

            <name>Apache 2</name>
            <comments>A business-friendly OSS license</comments>

        <name>The Organization Name</name>
        <url>The Organization web site URL</url>

            <id>The developer id</id>
            <name>The developer name</name>
            <email>The developer email</email>
            <url>The developer web site URL</url>
            <organization>The developer organization</organization>
            <organizationUrl>The organization web site url</organizationUrl>
                <role>Role #1</role>
                <role>Role #2</role>
                <picUrl>The developer picture URL</picUrl>

        <system>The issue management system, e.g. Bugzilla, TestTrack, ClearQuest, etc</system>
        <url>The issue management system web site URL</url>

        <system>The CI management system, e.g. Hudson,continuum, etc</system>
        <url>The CI web site URL</url>
                    <address>The sender email address</address>

        <url>The SCM web site URL</url>





How the report is created.

It is simple by using the “mvn site” command, please refer to my previous post.

Are there any outer world plug in?

Yes, sure. Why not? Maven also mentioned in their plug in page as well. Please travel to the lower part of that page you will see the outer world for sure. I hope we are enjoy traveling.


We have finished preparing our development environment so that we can ensure that there should not be any surprise during the integration with the very powerful “Maven” features, the “site”, especially the “report”. As I’ve mentioned, This is a final article for my first series.

The well preparing will help us to reduce the defect, on the other hand, if the defect is less, the working time is less, too. That mean we will have more time to do other things in my life. For me is writing this blog. Next I will move further to the detailed “Java/JavaEE” development with “Maven” and will do my best to post for sure. Please stay tuned as always.

Java Development with NetBeans and Maven: Part 4


We have configured our environment so that we can declare our own information outside the “Project POM File” (pom.xml) such as the “Subversion” user id and password, the “Issue Tracker” user id and password. But it is only the “Maven” universe. We live in the bigger one, the integration universe. That means we need to know the other integrated system universe. Even we configure our credential / personal information with purpose to let “Maven” to use them when it connect to each sever. It is just our credential / personal information. Since “Maven” acts as a client, it should provide credential / personal information itself, too. Normally these communication is done via the “SSL”, especially via the “HTTPS”. There are some good practice to which I would like share.

The HTTPS Good Practice For The Client

Most of integration universe has been configured and deployed under the “Apache HTTP” umbrella. As I’ve mentioned before, the “HTTPS” is preferred. This means the “Maven” will connect to them via the “HTTPS”, too. The “Maven” acts as a client, they act as a server for sure. What is the issues? Well, It is a very well known issue.

The Certificate Management For The Client

Normally the server provides its “certificate” to the client for initiating the “SSL” connection. The client will determine if this “certificate” can be trusted. If yes, the conversation will be initiated.

If not the connection will be dropped. We may face a trouble like we cannot connect to server system shows me something about “no trusted certificate found” or other close to this.

The HTTPS Client Configuration Good Practice

I am informing you about the good practice for the client side who would like to connect to the server via “HTTPS”. If the client is a “Java” environment, the “Server Certificate” should be injected to the “truststore”.

The “Server Certificate” is not only limited to the server certificate itself, but also the “Signer Certificate”, too. Please note the “Signer Certificate” is a certificate of the trusted authority who sign the “Server Certificate”. The signer also not be limited at one level, it can be more. It is called “Certificate Chain”. During the checking & verifying If any of “Certificate” inside this “Certificate Chain” is trusted, It will be determined as trusted. This means if we have 3 levels “Certificate Chain”.

The checking step is as following: –

  1. If the level 3rd is trusted, it is determined as trusted. The checking stop here.
  2. If the level 2nd is trusted, it is determined as trusted. The checking stop here.
  3. If the level 1st is trusted, it is determined as trusted. If not the system may show us as “no trusted certificate found”.

For me, I have 2 levels which are created by the “openssl”. Anyhow it can be a 1 level as a self-signed as well.

By default the “truststore” is as following:-

Table 1: The default truststore for JRE

Default Trustsore for JRE




Example: C:/Java.Application/Sun/Java/jre1.6.0_21/lib/security/cacerts

Table 2: The default truststore for JDK

Default Trustsore for JDK




Example: C:/Java.Application/Sun/Java/jdk1.6.0_21/jre/lib/security/cacerts

The injecting certificate command is as following: –

Table 3: The injecting certificate command

The injecting certificate command


keytool -importcert -trustcacerts -alias <MY_ALIAS> -file <Certificate> -keystore <Truststore>


Example: keytool -importcert -trustcacerts -alias myserver -file server.cer -keystore cacerts

Please note: you may be prompted to enter the password, the default password is changeit”.

Some of them are not default.

Some of them may have their own configuration environment instead, especially the “Subversion Client”. There are 2 types as global for whole client and per-user.

The server-wide






%ALLUSERSPROFILE%\Application Data\Subversion\servers

%ALLUSERSPROFILE%\Application Data\Subversion\config

%ALLUSERSPROFILE%\Application Data\Subversion\hairstyles




The per-user












I prefer to use the per-user instead. Please note, I’m a “Windows Vista”, my configuration home for “Subversion Client” is “C:\Users\Charlee.Ch\AppData\Roaming\Subversion”. Normally the per-user configuration is created automatically by the “Subversion Client”. If the “Subversion Client” does not trust the “Server Certificate”, you may face the message like this, “Server certificate verification failed: issuer is not trusted”. It can be configured easily by using the “Subversion Client” command via a command line, for me it is a dos prompt, as the following:

Table 4: Configure subversion client to trust the server certificate

Configure subversion client to trust the server certificate


svn list https://<YOUR_DOMAIN/svn/path/to/repository


Example: svn list

During executing this command, you will be prompted about the “Server Certificate”. Please press “p”, for accepting this certificate permanently. Anyhow the system may prompt you to provide the credential, please enter it properly. The top most certificate for the “Server Certificate Chain” will be stored at your local as the following: –

Table 5: The stored server certificate folder

The stored server certificate folder




Example: C:\Users\Charlee.Ch\AppData\Roaming\Subversion\auth\svn.ssl.server


At the moment, we understand that not only our credential / personal information should be configured, but also the “Maven” credential / personal information for itself should be configured, too. This will help us to achieve further integrating more simple and avoid the well know issues, such as the “HTTPS Client Configuration”. We are well prepared and ready for the next step, “Maven” integration with “Subversion” and “Issue Tracker”. I will post it soon, please stay tuned as always.

Java Development with NetBeans and Maven: Part 3


Since the Maven can integrate to the other system, such as “Issue Tracker“, “Version Control System“, especially the “Repository Manager“, which we will deploy our artifact for sharing to our team. All those target system is usually protected. We must provide the “security information / credential” such as user id and password for accessing it.

Normally we can declare the “security information /credential” inside the “Project POM File” (pom.xml). Please consider, in the real world development environment, they are many people joining the same project. The “Project POM File” (pom.xml) is also shared, too. If we decide to store that security information /credential” at the “Project POM File” (pom.xml). We may face a difficult if everyone keep updating the “Project POM File” (pom.xml) over and over. It would be nice that we can link the personal information, such as the security information /credential“, to the

Project POM File” (pom.xml).

Declare Our Own Information

You may have seen it berfore, The “settings.xml“. Please refer to my previous post, about the “Maven Repository Manager“, the “Artifactory” which can manage the repository and artifact for us. We use the “settings.xml” to notify “Maven” that it should connect to our “Maven Repository Manager“, the “Artifactory” instead of connect to the remote repository in the internet.

Inside the <profile> tag, we can declare a <properties> tag. The element inside this tag can be named any as we need. e.g. <userId>, and we can refer it in the “Project POM File” (pom.xml) by the ${MY_VARIABLE}, e.g. ${userId}. Pleases see further information here.

The we can declare our own “security information /credential” such as <issueUserId>, <issuePassword>,<vcsUserId>, <vcsPassword> and so on, so that we achieve configure our own “security information /credential“.


Special Feature for the Maven Repository Manager

We can declare our credential for accessing the “Maven Repository Manager“, please note the “Maven Repository Manager” usually anonymous downloading, but not for deploying.

        <id>The Reference Id</id>

The password encryption

It can be done by following this document. I will intoduce you an overview.

Create Master Password

Create the master passowrd
mvn –encrypt-master-password <password>

Store it for future referencing

Please create a file named “settings-security.xml” at <USER_HOME>/.m2 and put the following content into it.

  <master>Master Password</master>

Encrypt The Password

Create the master passowrd
mvn –encrypt-password <password>

Please copy the encrypted password and paste to the “settings.xml“, the <server> tag.

The Artifactory

If the security is enable for the “Artifactory“, we can not use the “clear password“, or take it to encrypt with the master password. The “Artifactory” encrypted value is required. The step for picking that vaule is as following: –

  1. Please log in to “Maven Repository Manager“, the “Artifactory“.
  2. Go to your profile page by clicking the name displayed at the top-right of the screen.
  3. Enter your current password and press “Unlock” button.
  4. The encrypted password will be displayed at the “Encrypted Password” text box.
  5. Copy the whole displayed value, including the {DESede} or other.
  6. You can use this value at the “settings.xml“, the <server> tag.
  7. You can also “double encrypt” by using the maven encryption, too.


At the moment we can declare our own information at the “settings.xml” and link it to the “Project POM File” (pom.xml). We also understand the special feature for the “Maven Repository Manager“, the password encryption, including the specific for the “Artifactory“.

Next I will make use of these to integrate with Version Control System, Issue Tracker, especially to create a report and maven site. Please stay tuned as always.

%d bloggers like this: