Robert, 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).
With that being said, it makes sense that you would want to make references to your OM objects using the OM and not the BaseOM. That way, all the methods inherited by OM from BaseOM always return OM objects as the OM object is what you should always use and you should NEVER directly use BaseOM. p.s. If you have set up ant FKey references within your <app>-schema.xml, you will notice that references to those objects within BaseOM inquestion always use the respective OM and not the BaseOM of the object referenced by the FKey. Hope this helps, Scott -----Original Message----- From: Robert Jenks [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 10:05 PM To: [EMAIL PROTECTED] Subject: Question about OM classes Hi, newbee here :-) I went back 3 months of list archives and couldn't find a mention of this, but I'll apologize in advance if it's been discussed before. Playing around with Torque (cool stuff dudes!) and have a question about the OM generated classes. I prefer to keep my auto-generated and human generated source files in separate directory trees, therefore I modified the om/Control.vm template and commented out the calls to ExtensionObject and ExtensionPeer so that the skeleton sub-classes don't get generated. I'll simply write them myself in a separate directory tree and compile both directory trees together. All is fine and dandy until I find that the Base classes won't compile without the sub-classes. Is there a reason that BaseFooEntity has multiple references to it's sub-class (FooEntity) or is this a template bug? This seems to be true of all the Base classes. They all depend on their skeleton sub-classes. Thanks, -Robert -- 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]>
