Date: 2004-12-21T02:20:27 Editor: RaphaelMankin <[EMAIL PROTECTED]> Wiki: DB Torque Wiki Page: TorqueFuture URL: http://wiki.apache.org/db-torque/TorqueFuture
no comment Change Log: ------------------------------------------------------------------------------ @@ -50,6 +50,9 @@ * Get rid of Texen? Maybe go XSLT? Use some different templating technique (while Velocity and Texen do a reasonably good job, their error reporting really lacks. Integration of the engine into other projects is also not really intuitive). (hps) + * Split the OM classes for tables into two layers: a base layer that is a pure value bean with just the user-declared fields and appropriate getters and setters, and a derived layer (equivalent to the existing BaseXXX classes) that has all the supplementary fields for foreign keys, and all the logic. There reason is that I want to be able to transmit DB objects over a network to a client that does not have access to the Torque run-time. At present I have to fiddle around with BeanInfo classes to prevent unwanted fields being transmitted, and code extra classes by hand. (RM) + + * Provide extra methods that clear down or invalidate all the supplementary fields such as the 'collXXX' arising from foreign keys. (RM) == Maven Plugin == --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
