Jon Stevens wrote:
> on 5/10/01 12:17 PM, "Martin Poeschl" <[EMAIL PROTECTED]> wrote:
>
> > sounds like a job for me ;-)
> >
> > i generated the classes with torque ...
> >
> > some the method names are different (e.g. getCreateDate() -> getCreated() )
> > should i change the interface (and also the LDAP classes)?
> > or add the methods to match the interface?
>
> Ok, the way to do this without breaking existing code and giving people a
> chance to migrate is to put the generated classes into a different package
> (you will have to do that anyway since the Peer objects are no longer in a
> .peer. package).
>
> Then, you essentially replace all the code in the existing methods/classes
> with calls to the new code in the new packages. The old stuff just becomes a
> thin wrapper around the new stuff. You mark everything in the old stuff as
> being deprecated.
>
> Make sense?
hmmm ... and what should happen to the interface???
should i add the methods like they are generated and mark the old ones as
deprecated too??
then i have to update the ldap stuff too ...
so the new interface will have the same methods as the generated classes ...
why do you think we need a different package name???
i think org.apache.turbine.om.security will work ... i can add the deprecated
method to the generated classes ...
> > i think it is no good idea to edit the BaseXyz classes (add the license, ...)
> > do we need them in cvs??
> > or should they be regenerated at build time?
>
> Right, they should be generated at build time. Take a look at how Scarab's
> build system does it.
>
> -jon
ok
martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
