Config Spring and DWR on Jetty with zero XML

I hate xml configuation files. They look awful. As a result, they can be very time-consuming to write, and are very error-prone. There's no type-safty checking whatsoever. I would rather keep configurations within my Java source code. After all, we programmers are the only people looking at these configurations, why create trouble for ourselves? Luckily, with annotation support in Java, we can now completely do away with xml files for developing Web applications. Here is my recent experience integrating Spring framework with DWR on a Jetty sever.

Spring Continue reading »

Create Multiple Modules Maven Project in Eclipse

Modularized software system design is often a good idea. Maven is the new software build system that is purported to be better than ant. For my new project, I want to create a maven build consisting of multiple modules. To do this, and let Eclipse treats these modules as parts of a single Eclipse project, I used the following procedure.

First create the top level maven project, which will be the container of the modules. Our top level maven project is called "cool".

Java time resolution

I am writing a Java program to run psychology experiments. Since this is a generic program that may be configured for running some reaction time (RT) experiments, I am worried about the time resolution of Java. It turns out that I don't need to worry too much, except on Windows. On Linux, one millisecond time resolution can be consistently achieved using either System.currentTimeMillis() or System.nanoTime() call. Continue reading »

Annoying when moving Java program from Windows to Linux

These day I write Java programs on my local machine and then move them to a Linux server to run experiments. This routine works fine so far. However, when I ran one of the progams, which involves coping one file from one directory to another, I kept on the following error message:

JBuilder "could not reserve enough space for object heap"

I have been using Borland programming environment since 1994, beginning with its Turbo C 2.0, then Borland C++, and now JBuilder. This company has always produced programmer friendly products. Comparing with other products, Borland's offering are always the most natural, and the easiest to get the job done. At least to me. Well, I mostly do Java programming these days. I have used all sorts of Java IDEs over the years. VisualCafe, VisualAge, NetBean, Eclipse, and so on. At the end, I still decided to settle on the tried -and-true Borland product: JBuilder.
Syndicate content
Nice place