[jira] Commented: (JS2-318) Upgrading to Torque 3.2-rc1 and to OJB 1.0.3

["Ate Douma (JIRA)" <je...@portals.apache.org>]

    [ http://issues.apache.org/jira/browse/JS2-318?page=comments#action_12317271 ] 

Ate Douma commented on JS2-318:
-------------------------------

In Torque 3.2-rc1 support for datatype BIT was dropped for Oracle !!!
Instead, (for Oracle) BOOLEANINT must be used.
This means that there is no single solution anymore (with Torque) for mapping a boolean to a database :-(
I can come up with only one solution which will work always on any db: 
replace BIT by BOOLEANINT and change the OJB mapping to INTEGER together with a Boolean2IntFieldConversion.
I've already done so have tested it out with HSQLDB and Oracle9i.
This now seems to work (as it should).

This means again a lot of schema changes (for db's which did support bit/boolean) but then,
the implementation of JS2-255 (column name changes: value -> column_value) yesterday already had a similar impact.
Thus, better do it now than after M4  ...


> Upgrading to Torque 3.2-rc1 and to OJB 1.0.3
> --------------------------------------------
>
>          Key: JS2-318
>          URL: http://issues.apache.org/jira/browse/JS2-318
>      Project: Jetspeed 2
>         Type: Improvement
>   Components: Persistence and DAO
>     Versions: 2.0-M4
>     Reporter: David Le Strat
>     Assignee: David Le Strat
>      Fix For: 2.0-M4

>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org