Skip to main content

Rolling out Java EE 6 development environment

Step 0 – Download and install JDK 6

Download JDK 6 from the link - Install it under c:\java.

Step 1 – Download and install JBOSS 6

JBOSS6M5 can be downloaded from the following link - Once downloaded unzip the file to c:\jboss6.

Step 2 – Download and install Eclipse

Eclipse Helios 3.6.1 can be downloaded from the following link - Once downloaded unzip the file to c:/eclipse

Step 3 – Install Maven 2 plug-in and extras

I will prefer to use Maven 2 as my build tool. This is very useful if we also have some continuous integration system set up in future. The Maven 2 eclipse plug-in update sites are located at - Launch Eclipse and install the plug-in core and extras. In case of the extras install only the WTP extension.

Once the M2E plug-in is installed,restarting Eclipse you may get some warnings as listed below:

Eclipse is running in a JRE, but a JDK is required
  Some Maven plugins may not work when importing projects or updating source folders.

You can resolve this by adding the following line to your eclipse.ini file. This file is located at c:\eclipse folder.


This is a snapshot from my eclipse.ini file


Step 4 – Install Subversion plug-in

I want to safe keep my learning on some subversion repository. So I went on to create a project on GOOGLE CODE called “windowshop” -

You can add the subversion plug-in for Eclipse using the following update URL -

Step 5 – Configure SVN

Now I will commit and change code kept on the Google Code SVN. So I need to add the code repository. You can do so easily by going to the SVN repository view and adding the following URL -

The development environment is more or less setup. If I see that I have missed anything going forward, I will try to add it here.


Popular posts from this blog

Why do you need Spring Cloud Config server?

Last month I wrote a primer on concepts around 12 factor app. Before getting into the details of the Spring Cloud Config Server, I must refresh on the principle #3 from the list presented in that post.

3 – ConfigurationStore config in the environments
Configuration information must be separate from the source code. This may seem so obvious, but often we are guilty of leaving critical configuration parameters in the scattered in the code. Instead, applications should have environment specific configuration files. The sensitive information like database password or API key should be stored in these environment configuration files in encrypted format.
 The key takeaways from this postulate for a cloud-native microservices application are:
Do not store configuration as part of the deployable unit (in the case of lead microservice - inside the jar or war if you are still deploying war like the good old days). Instead, store it in an external location and make it easily accessible during run-…

Changing the root web application in Tomcat 6

These days I am very busy developing a large and complex web application, which is nearing its first release. This web based product runs on Tomcat 6 and will be deployed on
But if I deploy my web application on Tomcat 6, I need to specify the context root. Well this is no good, why will the users of this website be willing to remember the context root. What if the context root changes. In other words the users would not be interest in typing the following - to visit this site.
Hence it is necessary that I change the default / root web application of Tomcat and point it to my application. I wanted to try and test this on localhost first. As always I Googled and found a number of posts and none seem to work. I also read the documentation it was helpful in understanding the concepts but was not effective as I could not get it working. Finally after few hours of trial and error one of my colleague Joyeeta Majumdar found the so…

Part 3 - Integrating Tiles, Thymeleaf and Spring MVC 3

In this post I will demonstrate how to integrate Apache Tiles with Thymeleaf. This is very simple. The first step is to include the tiles and thymeleaf-tiles extension dependencies. I will include them in the pom.xml. Note we wil lbe using Tiles 2.2.2Listing 1 - parent/pom.xml --- thymeleaf-tiles and tiles dependencies <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<!-- Tiles -->
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->