Mailing-List: contact jetspeed-dev-help@portals.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jetspeed Developers List" <jetspeed-dev@portals.apache.org>
Message-ID: <1845506496.1122862836508.JavaMail.jira@ajax.apache.org>
Date: Mon, 1 Aug 2005 04:20:36 +0200 (CEST)
From: "Chris Custine (JIRA)" <jetspeed-dev@portals.apache.org>
To: jetspeed-dev@jakarta.apache.org
Subject: [jira] Commented: (JS2-318) Upgrading to Torque 3.2-rc1 and to OJB
 1.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

Chris Custine commented on JS2-318:
-----------------------------------

Ate's suggestion would also fix JS2-160 which is something that has been a thorn in my side with J2 for a looooong time!  In case anyone is unaware of what JS2-160 is about, those of us using J2 with Postgres must maintain a modified torque-gen jar with a custom db.props for Postgres to map BIT types to int2.  I haven't had to tweak anything in quite some time since there haven't been any major schema changes, but I can tell you from reading Ate's suggestion that I believe it would fix this very old J2-160 issue.  Yay!

> 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