Having been working at the periphery of the Hibernate source and submitting simple patches for the Ingres dialect and some tests I am now in a position to start debugging some of the issues discovered whilst testing. I have been dabbling with building maven projects from Eclipse using m2eclipse, but have not managed to perform source level debugging. I found this article Dealing with the Eclipse IDE that provides some clues on how it is done.

Essentially it involves a remote debug session from a container project to a running maven goal configured to listen.

Versions

The versions of software that I’ve been playing with

• Eclipse Galileo ~SR1 – Build id: 20090920-1017
• Eclipse Helios M5 – Build id: 20100204-0846 (I started to install the m2eclipse plugin and import the projects, but needs more work)
• Ingres 9.3.1 (int.lnx/106)
• java version “1.6.0_16″
• mvn Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100)
• Apache Ant version 1.7.1 compiled on June 27 2008
• Hibernate 3.5.0-Final

Path: .
URL: http://anonsvn.jboss.org/repos/hibernate/core/tags/hibernate-3.5.0-Final
Repository Root: http://anonsvn.jboss.org/repos/hibernate
Repository UUID: 1b8cb986-b30d-0410-93ca-fae66ebed9b2
Revision: 19149
Node Kind: directory
Schedule: normal
Last Changed Author: steve.ebersole@jboss.com
Last Changed Rev: 19148
Last Changed Date: 2010-03-31 18:38:55 +0100 (Wed, 31 Mar 2010)


These notes assume that the software has been installed and configured. For example, the Maven local repository location is available and that the Maven remote repository is accessible.

Installing m2eclipse

The article Dealing with the Eclipse IDE includes links on how to install m2eclipse, but in summary, to install new software in Eclipse use the built-in update manager:

• Using the menus select
  • Help > Install New Software
  • In the dialog add the URL http://m2eclipse.sonatype.org/sites/m2e
  • Check the boxes of the packages that should be installed
    • NB” Version 0.9.8 should be un-installed before upgrading to 0.10.

Import the Hibernate project

Once the m2eclipse extensions have been installed into Eclipse the preparation for importing the Hibernate Project Object Model (POM) XML file into the IDE is complete. Importing the Hibernate project is optional and is only required if you intend to build Hibernate from Eclipse. The remote Java application perspective will connect to either a command line invoked maven process or an Eclipse invoked maven process.

• Start Eclipse
  • Create a new workspace for the Hibernate project.
• Using the menu File > Import
  • Select Maven > Existing Maven Projects
  • Click Next and use the browse button to specify the root directory of the Hibernate source code, this is the directory in which the top level pom.xml file exists.
  • The sub-projects appear in the tree view in addition to the hierarchy beneath the top level project.

The initial import and build of the workspace can take a while.

Create a Surefire Debug Configuration

Create a run configuration for a specific test class for debugging. In this example the filter.DynamicFilterTest has been cut down into filter.IngresDynamicFilterTest.

• Select the menu Run > Run configuration option or from the context menu using a right click.
• In the Run Configuration dialog select ”maven” and create a new configuration
  • Enter a name for the configuration
  • Surefire Debug
  • Set the base directory to the test suite directory by browsing the file system
  • Set the goals
  • test -Dmaven.surefire.debug
  • Use a JDBC profile if one is required and has been configured
  • Set the ”test” parameter to a specific test class intended for debugging
    • test=org.hibernate.test.filter.IngresDynamicFilterTest

Create a Debugging Container Project

The container java project does not contain any source and is used as the launch point for a remote debugging configuration.

• Using the File->New->Project->Java Project (or equivalent)
• Set the project name in the wizard
• Project Name: Maven Debug and finish

In order to debug a maven project a container project is used to connect to maven in debug mode.

Create Container Project from Ray Fan on Vimeo.

• Use the Run->Debug Configurations menu to create a configuration for the Remote Java Application
  • Set the nameName: Maven
  • Keep all the existing settings and apply

  

  • Select the Source tab and add source
    • File System Directory and browse to the Hibernate route source directory
    • Select the Search subfolders check box
    • Apply and close

    

• Use the Run > Debug Configurations menu to duplicate the Maven configuration for the Remote Java Application
  • Set the name
    • Name: Maven Debug
  • Change the port value
    • Port: 5005
  • Apply and close

  

Set breakpoints and start the test

At least one breakpoint should be set in the source prior to the run configuration Surefire Debug is started

• Browse the source tree in the package explorer to the test class
• Set a breakpoint
• Use the Run->Run Configurations menu and select the Maven->Surefire Debug configuration
  • Click debug to start maven

Eclipse breakpoint setting and starting maven from Ray Fan on Vimeo.

Using Eclipse to browse the project source and set a breakpoint prior to starting maven to run the test.

Start the debugger

• Use the Debug->Debug Configurations menu and select the Maven Debug remote debugging configuration
  • Click debug to start the debugging session
  • Switch to the debugging perspective when prompted
  • Once execution of the test starts the breakpoint set previously should be hit

Starting to debug from Ray Fan on Vimeo.

Starting to debug, switching perspective and hitting the breakpoint.

Related posts

• Hibernate 3.5.0-Final released
• Donnez-moi un café Ingres
• Rapid
• Ingres Migration Toolset
• Useful or useless? Follow on post …

Most notably, I extended the work started by Enrico Schenk in introducing additional Ingres dialects. There are now three possible dialects.

• IngresDialect – for use with Ingres II 9.2
• Ingres9Dialect – for use with Ingres II 9.3
• Ingres10Dialect – for use with Ingres II 10.0 – at the moment this is a place holder and uses the 9.3 dialect

The Ingres9Dialect switches uses the ISO date/time types and functions for mapping to their Hibernate equivalents. This changes the behaviour from the IngresDialect which used ingresdate type and functions.

Further changes to Ingres9Dialect will include the introduction of auto-increment columns; a whole host of additions will be required for the Ingres10Dialect and not forgetting the inclusions from the Ingres GeoSpatial project.
A list of new features introduced into each release is published on the “Ingres New Features Per Release” page.

Related posts

• Debugging the Hibernate project with Eclipse
• Useful or useless? Follow on post …
• In the market for JDBC properties
• Donnez-moi un café Ingres
• Google Summer of Code (GSoC) 2008

Java and JDBC applications seem to be the plat du jour and trying to peel away the layers getting to the JDBC settings and queries being executed in some of the frameworks can be a challenge.  Enabling JDBC tracing using a properties files requires the file being located within the CLASSPATH according to http://docs.ingres.com/Ingres/9.2/Connectivity%20Guide/jdbcdriverinterface.htm#o1237.  Many of the frameworks create the CLASSPATH environment based on files with specific extensions in specific directories, so what seems to be a valid directory in which to create iijdbc.properties can be a bit hit and miss.

Recently for me it has been necessary to set the system property ingres.jdbc.property_file as a parameter to the Java runtime.

A simple iijdbc.properties file enables logging and sets a couple of other properties created in for example, /tmp.
ingres.jdbc.lob.cache.enabled=true
ingres.jdbc.trace.log=/tmp/iijdbc.log
ingres.jdbc.trace.timestamp=true
ingres.jdbc.trace.drv=5
ingres.jdbc.property.timezone=NA-PACIFIC

The following passes the system property specifying the property file as an argument to the runtime environment executing a the class JdbcInfo and testing the connection to the imadb database.
cd $II_SYSTEM/ingres.lib
java -cp .:iijdbc.jar -Dingres.jdbc.property_file=/tmp/iijdbc.properties JdbcInfo jdbc:ingres://localhost:I17/imadb
Error establishing connection:
Communications error while establishing connection.

The connection failed and the log output from the command:
2009-04-24 13:25:03.788: Ingres Corporation - JDBC Driver [3.4.3]: Fri Apr 24 13:25:03 EDT 2009
2009-04-24 13:25:03.797: Ingres-Driver: registered
2009-04-24 13:25:03.805: Ingres-Driver.connect()
2009-04-24 13:25:03.812: Conn: lob.cache.enabled=true
2009-04-24 13:25:03.813: Conn: Connecting to server: localhost:I17
2009-04-24 13:25:03.853: MsgIo[0]: connection error - all addresses failed
2009-04-24 13:25:03.856: Ingres-Driver.connect(): error establishing connection
2009-04-24 13:25:03.856: Exception: 08001, 0xc4001
2009-04-24 13:25:03.856: Message: Communications error while establishing connection.
2009-04-24 13:25:03.857: Exception: null, 0x0
2009-04-24 13:25:03.857: Message: Connection refused
Although easily enough to spot from the command line the connection URL is incorrect in this case and the instance identifier should be II, but the log contains more detail.

Here’s the output from the successfully executed command after the instance identifier has been corrected:
java -cp .:iijdbc.jar -Dingres.jdbc.property_file=/tmp/iijdbc.properties JdbcInfo jdbc:ingres://localhost:II7/imadb
Ingres Corporation - JDBC Driver [3.4.3]: (JDBC 3.0)
INGRES [9.2]: II 9.2.0 (int.rpl/143)

Related posts

• Debugging the Hibernate project with Eclipse
• Hibernate 3.5.0-Final released
• Rapid
• Data Access Message Protocol – Wireshark dissector
• Ingres Migration Toolset

Ingres CAFÉ is a complete Web application development stack and runtime building upon Ingres 9.2.0, Ingres Eclipse DTP and various other Java and Eclipse components, details of which can be found on the project Wiki page.

Exemplifies mentored community development, congratulations.

Related posts

• Debugging the Hibernate project with Eclipse
• Vectorise your data
• Hibernate 3.5.0-Final released
• Learning to share
• Rapid

Being a tomcat, JSP and OpenLaszlo nubbie I managed to get the Amazon Store demo to use Ingres for the checkout and shipping address details. A couple of JSPs a two line change in OpenLaszlo source and the demo was reading data from Ingres. The code changes took 5 minutes, getting it to work took a little longer. I used OpenLaszlo 4.0.7 for my tests but OpenLaszlo 4.0.8 is now available.

Take a look at the OpenLaszlo source code at the line
<dataset name="dsAddressList" src="data/addresses.xml"/>
<dataset name="dsCreditCardList" src="data/creditcards.xml"/>


These were modified to
<dataset name="dsAddressList" src="/ingdb/getaddress.jsp" request="true" type="http"/>
<dataset name="dsCreditCardList" src="/ingdb/creditcard.jsp" request="true" type="http"/>
Setting request=”true” causes the client to request data each time the query string or the base URL changes.

My initial pages and tomcat configuration is documented on the page “Accessing data from JSP” and contains the simple DDL for the table and some sample data. In this example the database and credentials are embedded in the page. With a little more time I changed the JSP to use the JSTL and configured the tomcat server with a JNDI resource for the database connection. My latest attempt is document on the page “JDBC and JNDI”.

For 2008 the watchword is “Rapid”. Rapid application development and deployment, everything has to happen faster. Using an environment like OpenLaszlo gets part of the way there.

We’ll be looking at subject matter for a development sprint at the forthcoming UK IUA in June. An OpenLaszlo application may be a candidate.

Related posts

• Debugging the Hibernate project with Eclipse
• Ingres Migration Toolset
• Hibernate 3.5.0-Final released
• Button clicks do nothing in Ingres Database Workbench, Eclipse and its derivatives
• In the market for JDBC properties