The BaseXXX and BaseXXXPeer classes will be overwritten but XXX and XXXPeer classes will not be overwritten if they already exist.
Move your application logic into XXX and XXXPeer. As a rule you should not change the Base classes ... On Fri, Sep 27, 2002 at 02:39:06PM -0400, Bruce Altner wrote: > Greetings: > > I'm in the initial stages of my second Turbine-based application and find > that I have to extend the behavior of one of my custom-defined Peer > classes. I have done this already and it works fine. However, as the > project progresses I will very likely need to regenerate the Peer classes > from time to time (at least that's what happened in my first project) and > this will "erase" the changes I've already made, since these were code > changes rather than changes to the schema itself. > > Is there a recommended way to prevent this from happening? I guess I could > always pull the extended class out of CVS but I was thinking that there > might be a better way, e.g., one that didn't overwrite extended classes > each time I need to execute the ant "project-om" target. > > Thanks, > Bruce > > > -- > 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]>
