I downloaded Torque 3 this weekend and spent some time working with it, I'm
impressed -- this is nice package.

I was surprised to see the tight coupling of data access objects and data
objects though.  What I observed is that if I set "torque.addSaveMethod =
true" it does two things.  First (in BaseXXX classes) is that Torque
generates the setXXX() methods to include a test to see if the new value is
different from the current value, and if so calls setModified().  Second
Torque generates a save() method in the BaseXXX classes.  If I have
addSaveMethod set to false then I don't get the "setModified()"
functionality and I also don't get the "save()" methods.  *BUT* the
generated BaseXXX classes still have a private static reference to the
XXXPeer object.

Is there a way to generate the base classes _with_ the setModified()
functionality, but no save() method and no reference to the peer object?  I
want to be able to generate code that closely models the J2EE "Data Access
Object" and "Value Object" patterns.

Joe

Reply via email to