If you select database dialect of DB2400, the driver class name is populated with:

COM.ibm.db2.jdbc.app.DB2Driver

which is the DB2 UDB class name.

It should be

com.ibm.as400.access.AS400JDBCDriver

which is the IBM Toolbox for Java JDBC driver for DB2 UDB for iSeries

Also, is the Hibernate toolbox for eclipse ever going to support Eclipse 3.0 ?

The issue I have (and I suspect many other developers) is that the Eclipse version we use is the one that the heavyweight IDE manufacturers chose when they released their products, so in my case, I cannot use the plugin within my IDE, because I use RAD 6, which is Eclipse 3 based, not 3.1.

What does Eclipse 3.1 give us plugin wise that Eclipse 3.0 doesn't ?

PS this is in the create hibernate configuration file wizard

report the dialect issue in jira - thank you.

And no, we won't support eclipse 3.0.

And what does eclipse 3.1 gives you ?
Performance, Performance, Performance
Better expandability and some more richer API's which we utilize.
All new development of webtools project is on eclipse 3.1 which we also use

OK, will report the bug in Jira.

Don't worry I am not on a holy crusade to get an Eclipse 3.0 version, was just wondering how many professioanl developers using commercial heavyweight IDE's are stuff with pre Eclipse 3.1 IDE's and therefore can't use the plugin in situ.

As it stands we use RAD6 for devlopment, and have a separate install of Eclipse 3.1 with the plugin installed, which is OK, but not ideal, as you are cosntantly synching stuff in and out of the two workspaces rather than having it all in one place.

Having said that, its still miles faster with the plugin than all the previous manual coding.

eclipse 3.1 has too many benefits to stay at 3.0 just for RAD/WSAD users...sorry.

No probs, I'm sure IBM/Rational will bring out an update soon anyway, with any luck, nicely coinciding with the the production release of the tools.

I put the buggette on Jira by the way.