Does this mean the security service becomes unusable outside the tdk? I
do not like that idea.
john mcnally
Martin Poeschl wrote:
>
> Jason van Zyl wrote:
>
> > On 7/4/01 4:03 PM, "Martin Poeschl" <[EMAIL PROTECTED]> wrote:
> >
> > > i would like to move the generation of the om/peer classes to tdk to give
> > > end-users a chance to extend the classes without subclassing anything.
> > >
> > > comments?
> >
> > Can you be more specific about the changes. I would assume we
> > keep all the interfaces in the turbine repository than generate
> > everything in the TDK, yes?
>
> yes.
> only the generated files + files overriding them (e.g. TurbineRole,
> TurbineRolePeer, ...) will be moved.
> The DBSecurityService, UserManager, interfaces (User, Role, ...) will stay in
> the turbine repository.
>
> to extend TurbineUser you only have to extend turbine-schema.xml, but if
> generated classes are included in turbine.jar you have to rebuild turbine.
> if we move the generated classes to tdk, users are able to extend e.g.
> TurbineUser without recompiling turbine.
> and they don't have to write their own UserManager, ..
>
> martin
>
> ---------------------------------------------------------------------
> 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]
