GraphHopper – A Java routing engine

karussell ads

It took me some time to collect the hibernate.cfg.xml data which is necessary for derby, oracle and h2. So here are the default settings for those databases:

1. Apache Derby (network)
   You start the network server and specify the following options in the script:Linux: DERBY_OPTS=”-Dij.driver=org.apache.derby.jdbc.ClientDriver -Dij.protocol=jdbc:derby://localhost:1527/ -Dij.user=admin -Dij.password=admin”
   Windows: set DERBY_OPTS=”-Dij.driver=org.apache.derby.jdbc.ClientDriver -Dij.protocol=jdbc:derby://localhost:1527/ -Dij.user=admin -Dij.password=admin”

   <property name=”hibernate.connection.driver_class”>org.apache.derby.jdbc.ClientDriver</property>
   <property name=”hibernate.connection.url”>jdbc:derby://localhost:1527/databaseName;create=true</property>
   <property name=”hibernate.connection.username”>admin</property>
   <property name=”hibernate.connection.password”>admin</property>
   <!– no schema necessary –>
   <property name=”hibernate.dialect”>org.hibernate.dialect.DerbyDialect</property>

2. Oracle (thin)
   <property name=”hibernate.connection.driver_class”>oracle.jdbc.driver.OracleDriver</property>
   <property name=”hibernate.connection.url”>jdbc:oracle:thin:@host:1521:databaseName</property>
   <property name=”hibernate.connection.username”>YOURSCHEMA</property>
   <property name=”hibernate.connection.password”>YOURPASSWORD</property>
   <property name=”hibernate.default_schema”>YOURSCHEMA</property>
   <property name=”hibernate.dialect”>org.hibernate.dialect.OracleDialect</property>
3. H2
   <property name=”hibernate.connection.driver_class”>org.h2.Driver</property>
   <property name=”hibernate.connection.url”>jdbc:h2:path\databaseName</property>
   <property name=”hibernate.connection.username”>sa</property>
   <property name=”hibernate.connection.password”></property>
   <property name=”hibernate.default_schema”>PUBLIC</property>
   <property name=”hibernate.dialect”>org.hibernate.dialect.H2Dialect</property>

To make it complete here are the maven settings for the databases:

1. Apache Derby (network)
   <dependency>
   <groupId>org.apache.derby</groupId>
   <artifactId>derbyclient</artifactId>
   <version>10.4.2.0</version>
   </dependency>
2. Oracle (thin) no public version is available but you could install the jar file into your local repository or into an archiva repository via:
   mvn install:install-file -DgroupId=com.oracle -DartifactId=ojdbc6 -Dversion=11.1.0.7.0 -Dpackaging=jar -Dfile=/path/to/file<dependency>
   <groupId>com.oracle</groupId>
   <artifactId>ojdbc6</artifactId>
   <version>11.1.0.7.0</version>
   </dependency>
3. H2
   <dependency>
   <groupId>com.h2database</groupId>
   <artifactId>h2</artifactId>
   <version>1.1.102</version>
   </dependency>

There are several tools to measure the code quality of my free timetabling software TimeFinder. Here are the tools I tried with success:

• FindBugs (latest version 1.3.8) – uses static analysis to look for bugs in Java code. This is a great tool, it discovered possible NullPointerExceptions and a lot more bugs in my projects. Sometimes I asked myself how this program could have discovered this ‘complicated’ bug.With the maven plugin you can do:

  mvn findbugs:findbugs

  which will use version 1.3.8 out of the box

• PMD (latest version 4.2.5) – scans Java source code and looks for potential problems. The rules are configurable, but at the beginning you will only need the provided one (and spend a lot of time to choose your favourites ;-))In NetBeans 6.5 this tool is well integrated and works like a charme (CTRL+ALT+P).With the maven plugin you can do:

  mvn pmd:pmd

  after you specified the following in the pom.xml under<reporting> <plugins> :

  <plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-pmd-plugin</artifactId>
    <version>2.3</version>
    <configuration>
      <targetJdk>1.5</targetJdk>
    </configuration>
   </plugin>

Other tools could be

• JarAnalyzer – Is a dependency management utility for jar files. It’s primary purpose is to traverse through a directory, parse each of the jar files in that directory, and identify the dependencies between the jar files.
• HammurAPI – a code quality governance platform

but I didn’t tried them so far.

For Findbugs  and pmd there is a NetBeans plugin (SQE … software quality environment) which looks promising, but fails with a NullPointerException after I installed it via the update center and tried it on my project. Maybe I should use one of the snapshots. (BTW: I successfully used the pmd-plugin and findbugs in the standalone version).

Sonar is another interesting approach to use several code quality tools at a time. With Sonar it is possible to see the violations or possible bugs over das or weeks  – so, you are looking at the improvements and you will not get lost in the mass of bugs at the beginning. Another “multi-tooling” project is XRadar.

A little bit offtopic, but a great tool is proguard, which shrinks, optimizes, obfuscates and preverifies Java class files. There is even a maven plugin for that.

If you want no server side setup for webstart all your clients must have a java version greater than java6 update 10 (the naming convention gets too complicated now, mr. sun! …)

For ubuntu 8.04 see my last blog entry how to install this java version.

All you need to do in our maven set-up of this post is to add the following 2 lines to our pom.xml:
…
</sign>
<pack200>true</pack200>
<gzip>true</gzip>
<verbose>true</verbose>
…

Then do:
mvn clean install webstart:jnlp
again and add one line

<j2se version=”1.6+” initial-heap-size=”32m” max-heap-size=”128m”/>
<property name=”jnlp.packEnabled” value=”true”/>

to our jnlp template.

And as it is described here you could even use the versioning feature
<property name=”jnlp.versionEnabled” value=”true”/>
with a specific naming convention, too:
foo__V1.0.jar

But all only if the clients have java > java6 update 10 …

Start TimeFinder here to try a servlet-free-packed200 application out. With jars it was approx 9 MB. Now all pack.gz files in sum are 3.3 MB! And the download time was approx 160 seconds, where now I downloaded und unpacked it within 40 seconds with the same internet connection. You can try it for yourself via switching the java version e.g. from java6_10 to 6_7 or to java5 (in ubuntu this is relative easy with ‘sudo update-alternatives –config javaws’) But before you have to remove the application from cache: start javaws -viewer, search TimeFinder’s shamrock and remove it. Otherwise TimeFinder would start nearly instantaneous.