On this question of non regenerating the BaseXXX classes, they haven't been fully useful for me. For example, I have wanted to add to the velocity templates a custom method that I would like to be part of all the BaseXXX classes. Torque isn't able to accommodate this, once the classes have been built.
I might suggest this: that torque alway regenerate the BaseXXX classes, but it "honors" a section of the file and retains any of your changes. For example, in the generated BaseXXX files there could be markers which denote the beginning and end of custom changes. Then Torque would generate a new BaseXXX file based on the template, but insert the code between markers in the new BaseXXX file. Doesn't that sound cool? Dan -----Original Message----- From: Daniel Rall [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 05, 2001 12:12 PM To: Turbine Users List Subject: Re: Question about OM classes "Weaver, Scott" <[EMAIL PROTECTED]> writes: > The idea behind separating your OM objects into 2 classes BaseOM and OM, is > that you are able to make mods to the OM and not worry about Torque writing > over the top of it if you run "ant init" (Torque only re-generates the > BaseOM and not the OM). You can think of them as two halves of the same class. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
