I posted a note similar to this a couple days ago, but it got lost in the shuffle.. I don't mind helping on the solution. As a shorterm fix, I started using my wonderful ( ;-) ) class TurbineHack. I've attached to this email.
With some direction on which way to proceed, I can definitly help... Eric -----Original Message----- From: Humberto Hernandez Torres [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 4:21 PM To: [EMAIL PROTECTED] Subject: turbine and decoupled torque I am running my application with turbine and the decoupled torque but I am having some problems. The org.apache.turbine.util.parser.BaseValueParser class knows about org.apache.turbine.om.NumberKey but since I am using the decoupled torque the fields are actually org.apache.torque.om.NumberKey. I can make a patch so it can handle both values and hope there are no other issues like these. The alternative is to make org.apache.turbine.om.NumberKey inherit from org.apache.torque.om.NumberKey and start referencing org.apache.torque.om.* from everywhere else instead of org.apache.turbine.om.* . The situation is the same for StringKey and I susspect for other classes as well. Do you guys have any indication on how to proceed? -- Humberto -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
TurbineHack.java
Description: Binary data
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
