I have an number of applets that are served up via turbine/velocity
templates, and require access to the getters/setters on my [nested]
Torque om objects. My first reaction is to write a parallel set of bean
classes for passage to the applets via serialization - this way, the
applets do not see Torque interfaces. A problem with this approach
however, is that the marshalling code for om<->bean conversion promises
to be tedious to write and maintain.
I suppose I could also write an ant task to generate the code for me
(like TorqueObjectModelTask), however this seems like overkill too.
Is there a less painful way to make Torque data available to the applets?
Thanks.
J.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
