[ http://issues.apache.org/jira/browse/TRB-5?page=comments#action_12330120 ]
Henning Schmiedehausen commented on TRB-5: ------------------------------------------ You are using Torque 3.2-rc2 and I use Torque 3.1.1. Turbine also uses 3.1.1 to generate the OM classes. That might be the problem. Can you try with the 3.1.1 runtime? If this is the problem, then IMHO it is a Torque problem, because it should be backwards compatible between the 3.1.1 release and 3.2. I don't intend to build the OM classes with 3.2-rc<x>, because I do want to stick to released versions for 2.3.2, which might be the last release for a longer time. Another thing that you can try is to build custom peer objects for an application (again, get the secdemo and just substitute the 3.1.1 for 3.2 versions) and check whether the Torque Security Service chokes on the 3.2 built peer objects. Currently I tend to point the finger at Torque. ;-) > TorqueSecurityService relies on a datasource named "default" > ------------------------------------------------------------ > > Key: TRB-5 > URL: http://issues.apache.org/jira/browse/TRB-5 > Project: Turbine > Type: Bug > Components: Turbine 2.3 > Environment: Turbine-2.3.2-rc2.-dev > Reporter: Thomas Vandahl > Assignee: Henning Schmiedehausen > > The OM-classes generated during the build process of Turbine need a > hard-coded data source called "default". > The previous version simply used the configured default DataSource as in > torque.database.default=turbine -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
