[birt-dev] CHECKIN: Derby library compatibility fix for SampleDB data so

["Gary Xue" <gxue@xxxxxxxxxxx>]

- Summary:

Checked in a workaround to allow BIRT SampleDB data source to work in a application which embeds a different version of Derby

 

- Bugzilla Bug(s) Resolved:

132017 reports using Derby database don't work with glassfish server

142285 Derby: Failed to start database on datasource create panel

 

- Description:

Due to Derby limitation (http://issues.apache.org/jira/browse/DERBY-1228), each JVM can only contain one instance of Derby engine. This causes a problem for BIRT deployment into an application which packages an older version of Derby. BIRT SampleDB will stop working in such a case.

 

This checkin employs a workaround to use a custom class loader to ensure that BIRT SampleDB plugin only loads its packaged version of Derby JAR file. It does not guarantee that BIRT will co-exist happily with other Derby-embedding components in the same JVM. However it does make sure that if BIRT is the only active Derby user in the application, it will always load the right version of the derby library.

 

Also included a fix to the oda.jdbc driver so that when a chained SQLException occurs all the exception messages are displayed.

 

- Tests Description:

Manual test

 

- Notes to Build Team:

 

- Notes to Developers:

 

 

- Notes to QA:

 

 

- Notes to Documentation:

 

- Files Edited:

"/org.eclipse.birt.report.data.oda.jdbc/src/org/eclipse/birt/report/data/oda/jdbc/JDBCException.java"

 

"/org.eclipse.birt.report.data.oda.sampledb/src/org/eclipse/birt/report/data/oda/sampledb/SampleDBJDBCConnectionFactory.java"

 

- Files Added:

 

- Files Deleted: