> > After my OM classes have been generated I add methods that
> > are specific for
> > certain tasks. For example I already mentioned the Product
> > table to which I added
> > doSelectWithVendor(). As another example - I had to move
> > records to a "deleted
> > items" table when they became stale. I added an expire()
> > method to the Data
> > Object to handle this for me. This list could go on - there
> > are always
> > non-standard things do to depending on your application design.
>
> Perhaps the OM generated classes should be called something
> like "FooOMBase", and you could extend them to add your
> functionality. That way (in theory) regenerating the OM
> classes would not wipe out your changes.
>
There is some problems with this approach (see mail archives). There has
also be some solutions suggested which I looking at as we speak.
~ Leon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
