Roo dbre for Sybase - don't use jtds, try JConnect

Just wanting to share my recent experience in case it is helpful to anyone.

Using Roo 1.2.2 and the jtds 1.2.4 wrapper - the generated schema had name="" for all foreign-key elements.
Eg:
<table alias="Evibs" name="testTableUser">
<column name="au_lname" primaryKey="true" required="true" scale="0" size="40" type="12,varchar"/>
<foreign-key foreignTable="testTablePhil" name="" onDelete="restrict" onUpdate="restrict">
<option key="foreignSchemaName" value="Evibs"/>
<option key="exported" value="true"/>
<reference foreign="au_lname" local="au_lname"/>
</foreign-key>
<unique name="testTableU_4890527781">
<unique-column name="au_lname"/>
</unique>
<unique name="au_lname_index">
<unique-column name="au_lname"/>
</unique>
</table>

The root cause of this is an issue between the jtds driver and the Sybase sp_fkeys system procedure call. Refer to:
http://sourceforge.net/projects/jtds.../topic/3464175

The end result is that I moved to the jConnect (Sybase's) JDBC driver Version 6.00

I wrapped this by making a new wrapper for jConnect based on: https://github.com/SpringSource/spri...9/jtds/pom.xml

Built this and installed in Roo 1.2.2 and now both introspect and reverse are working.

If anyone is facing a similar issue, would be happy to provide additional info.