[JS2-318] Upgrading to Torque 3.2-rc1 and to OJB 1.0.3

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-M4
• Fix Version/s: 2.0-M4
• Component/s: Persistence and DAO
• Assignee: David LeStrat
• Reporter: David LeStrat
• Created: 31/Jul/05 08:13
• Updated: 12/Sep/05 00:09
• Resolved: 12/Sep/05 00:09

Description

I have been doing some tests and I think we should upgrade Torque (to 3.2-rc1) and OJB (to 1.0.3) for the following reasons:

1. Torque: Now supports derby for SQL generation. Also, issues with cascading delete and HSQL have been fixed. This will address http://issues.apache.org/jira/browse/JS2-227.

2. OJB: Quite a few bugs fixed. Also, I noticed a couple of weird behaviors with the current version:
As I mentioned in a previous email:

• AbstractRegistryTest: the assertion on line 198 (assertNotNull("Web app did NOT persist its description", webApp.getDescription(Locale.FRENCH)) works no matter what locale is passed. I tried Locale.getDefault(), as well as Locale.FRENCH and it does not seem to matter. With 1.0.3, the assertion only works for Locale.FRENCH. Which the right correct behavior.
• TestUserInfoManager: When testing with ExtendedPortletMetadata, I do not quite understand how
  it ever worked without calling updatePortletApplication on the registry. With OJB 1.0.3, you need to update the portlet application with the new loaded metadata for the test to pass. Just seem to make sense
  to me.

I have applied the changes locally, I re-ran all the tests and everything is working, including the deployed application.

Issue Links

• is related to: JS2-366 Clean up orphan tables in J2 DB schema