Extened user seems to work okay for me in TDK 2.2B3, But I am using the
fulcrum classes.
Then again, I'm not doing anything complex with it.
<table name="TURBINE_USER" javaName="OpencourseUserImpl"
alias="TurbineUser"
baseClass="org.apache.fulcrum.security.impl.db.entity.TurbineUser"
basePeer="org.apache.fulcrum.security.impl.db.entity.TurbineUserPeer">
<column name="USER_ID" primaryKey="true" required="true"
type="INTEGER"/>
</table>
Hope that is of some relevance.
Derick
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 18, 2002 6:08 AM
Subject: RE: When will TDK 2.2 be released?
> I definitly agree that having a working extend user is crucial for 2.2.
The
> other one I would toss out (although the scope might be too much) is to
> integrate the new Security schemes that have been tossed out.
>
> I think doing those two things would give people a reason to upgrade to
2.2,
> versus staying with 2.1. Right now, while the decoupled stuff is cool, it
> adds more complexity as well. And doesn't seem to be a compelling reason
to
> upgrade. Fixing the extend user abilty and pluggable security do seem
> compelling.
>
> Eric
>
> -----Original Message-----
> From: Scott Eade [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 18, 2002 7:25 AM
> To: turbine-user
> Subject: Re: When will TDK 2.2 be released?
>
>
> > From: Martin Poeschl <[EMAIL PROTECTED]>
> >
> > there is no release date planned :-(
> > but you should definitly start with 2.2 and report any problems!!
> >
> > 2.2 works fine for my apps, but we need more testing before a final
> release
> >
> > martin
>
> Martin,
>
> Surely there must be some kind of features based target for a 2.2 release,
> otherwise there will only ever be 2.2 beta releases until the end of time.
>
> I think we need to come up with a list of requirements that need to be met
> in order to declare a turbine/tdk 2.2 final release. I would imagine this
> list might include:
>
> 1. A release of torque 3.0 final (we need to start the same discussion on
> the torque-dev list with respect to torque).
> 2. A release of maven 1.0 final (I would imagine the maven guys have some
> fairly specific criteria in mind for their 1.0 release).
>
> I would like to add my personal bugbear to the list:
>
> 3. A working, documented solution to the requirement to extend the
> turbine_user table.
>
> Surely there is room for a process here? Why can't the committers and
users
> of turbine nominate the requirements for a 2.2 final release (features,
> fixes, issues, etc.) These can be voted upon individually and the
accepted
> ones added into the todo page on the turbine-2 site. This would provide
> something for the contributors to work towards and a better answer to the
> "when will turbine 2.2 be released?" question than "nothing is planned".
>
> I am happy to try and coordinate some of this, but if anything is going to
> be done then the committers and users of turbine need to step forward with
> their lists of critical requirements for the 2.2 release.
>
> What do you believe are the things that need to be done before a
turbine/tdk
> 2.2 final release can be realized?
>
> Cheers,
>
> Scott
> --
> Scott Eade
> Backstage Technologies Pty. Ltd.
> http://www.backstagetech.com.au
>
>
>
> --
> 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]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
