I would like to suggest changing the Torque Object.vm template to
use a variation of the JavaName parameter to create the object field 
names instead of using the DB column name.  My reason for wanting to 
do this is so that bean introspection of the field name would find the
appropriate setters and getters.

I needed to do this because a client mandated using Struts and I 
wanted to use the O/R capability of Torque.  This change allowed
me to use the autogenerated objects from Torque directly as beans in 
the tag libraries of Struts. A co-worker of mine had already made this 
change in a 2.2 version of Turbine/Torque because of some introspection 
he was doing. I used his Object.vm as an example to make the changes to 
the latest 3.0 cvs version of Torque.  

Neither one of us is very familiar with Velocity so our solution is 
probably a hack, but I could submit a patch file as a starting point 
if others would find this useful.


Steven F. Davis

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to