Torque initially generates 4 OM/Peer classes (as well as a MapBuilder)
from the xml schema.
BaseFoo BaseFooPeer
Foo FooPeer
You should never make any references to BaseFoo or BaseFooPeer. As the
best way to consider the arrangement as two classes Foo and FooPeer with
the other classes providing a place to safely regenerate code to
add/remove functionality from Foo and FooPeer. Foo and FooPeer will
only be generated as long as they do not exist, as it is expected that
you will add business logic to these classes. In order to account for
schema changes BaseFoo and BaseFooPeer are overwritten for any change in
the schema.
John McNally
Jim McNeill wrote:
>
> Having seen the reception that novices get in this list, I get the feeling
> that I'm really going to regret this, but here goes.
>
> I honestly have downloaded the TDK and got the example app going, and
> amended it a bit OK. It lead me to ask several questions, which I'm having
> difficulty answering from the howtos and other docs. I've had a look through
> the mail archives too, but I'm still none the wiser. I'll pose just one of
> my questions, so that you can gauge the frightening extent of my ignorance:
>
> Em, Turbine is an application generator, yeah? It creates java code from an
> XML representation of database structure, plus some Velocity screen and
> layout definitions. You add your business logic into the generated Java
> code. So, standard question for code generators, how do I preserve my
> business logic when I decide to add a few fields and generate the lot again?
>
> And you thought I was joking when I said I was thick.
>
> Cheers
> Jim McNeill
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
