> If anyone's tried to use Torque to build the Turbine schema recently
> they may have noticed that it's broken. This is because the Velocity
> Texen StringUtil class got broken when a change was made to
> Velocity API
> for passing list literals into methods. I've submitted a patch to the
> velocity-dev list so this issue should be fixed soon...
Are the Turbine schema OM classes being generated with Torque?
This would be great, and it would be possible to get rid of
at least one piece of code: util.db.map.TurbineMapBuilder,
which should be replaced with the auto-generated map builders
for each table.
> Sean Legassick
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
