DBRE and DB2400

[Alan Stewart]

I believe I have resolved the issue, but will need you to test as I don't have access to a DB2/400 db as mentioned before. At least the driver is instantiated and not null

Alan

[pgrimard]

Well you're quicker than I was, lol.

It Worked!!! It is absolutely genius! It had no trouble determining the nearly 400 schemas in my database. I ran both introspect and dbre on my personal schema which doesn't have too many tables in it, and it all worked out just fine.

Truly an amazing tool! Btw, will you be in Chicago for SpringOne2GX?

[Alan Stewart]

That's great news it worked for you. The timing was excellent as well, as Ben and myself had committed a lot of performance enhancements a few days ago (ROO-1506) which made schemas with 400+ tables perform a lot better than before.

I can't make SpringOne unfortunately but Ben and Stefan will be there.
Alan

[Alan Stewart]

I had a regression bug as raised by myself in ROO-1528 that affects the referencedColumnName in the @JoinColumn annotation, so get the code and do a new build or wait for RC1.

[kcbaltz]

I've just downloaded the 1.1.0-RELEASE version of Roo and it appears to still have this issue. I'm new to Roo, so there's a strong chance I'm doing something wrong, but I am getting the error message described originally in this thread. Here are the steps I've taken


roo> persistence setup --provider HIBERNATE --database DB2400

I have edited database.properties to fill in the hostname, username, and password.

I'm trying to introspect my library using the following:

roo> database introspect --schema MISKCB
No remote OBR repositories have matching add-ons matching your request
JDBC driver not available for 'com.ibm.as400.access.AS400JDBCDriver'


Anything I'm doing wrong?

[kcbaltz]

I spoke too soon. Just after posting, I came across an instruction to run the following:

script install-jdbc-drivers.roo

That installed whatever Roo was missing and now I can introspect successfully.

[pgrimard]

In case you're still wondering why you had to do this, the reason is because the JTOpen jars and a handful of other 3rd party database jars are quite large. The JTOpen I think is around 6MB+. Bundling all of those as OSGI wrapped bundles would result in a heavy download for the Roo distribution and could progressively get bigger as more database support is added. This script keeps things lightweight since not everybody wants those 3rd party libraries.

btw, I'm glad to see I'm not the only one using DB2400

[kcbaltz]

That makes sense, but it does suggest that Roo should prompt you to run that script when you do the persistence setup and tell it you want to use DB2400. Or possibly when you get that "driver not found" error.

[Alan Stewart]

Appended reminder about running install script to exception message

[Alan Stewart]

Out of interest, has anyone attempted to connect to DB2 for Windows/Linux using the DB2/400 driver?