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-…

Upgrading Lead Microservice - Use MariaDB and Flyway with Spring Boot

So far I have been using an in-memory H2 database or Mockito for testing the lead microservice. To make the transition towards using the Spring Cloud Config server, I need to upgrade the micro-application to use MariaDB. I will be adding the configuration in the application.yml  the file which in the subsequent post will move over to the config server store. I will also be using Flyway to make it easy to maintain the database schema changes in future. I will use this post to introduce Flyway in the mix. Spring Boot also provides first class integration with Flyway. I am using Flyway as its really quick and easy to get started, minimal learning curve (no DSL) and I am comfortable with it having used it in the past.


MariaDB 10 is installedBasic familiarity with FlywayHeidi SQL client is installed.
Step 1 - Update build.gradle to include the MariaDB JDBC and Flyway dependencies.
Do not forget to do a Gradle refresh on your IDE (I am using STS 3.8.4 on Java 8)

Step 2 - Rename the…

How to implement Cache Aside Pattern with Spring?

ProblemYou want to boost application performance by loading data from a cache and prevent the network trip to the persistent store (and also the query execution). This can be achieved by loading data from a cache. However, you want to load data on demand or lazily. Also, you want the application to control the cache data management – loading, eviction, and retrieval. Forces Improve performance by loading data from cache lazily.Application code controls cache data management.The underlying caching system does not provide read-through, write-through/write-behind strategies (strange really ??).
Solution Use cache aside design pattern to solve the problems outlined above. This is also one of many caching patterns/strategies. I believe it is named in this because aside from managing the data store, application code is responsible for managing the cache also.
Let's now try to understand how this caching technique works and then explore how it solves the problems.
ReadCache MissThe applic…