Your best bet would be to live with it for the time being. There are quite a few issues with the Security service that aim to be fixed with newer versions. Curious, why are you not liking them?
You can alternatively check out the source from cvs, install maven, change the PeerClasses (org.apache.turbine.om) to use the native id generation and recompile. Read up on Torque to see how Peer classes are affected depending on the id scheme you select. Good luck, Chris > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 03, 2002 4:45 PM > To: Turbine Users List > Subject: TURBINE_* using native seqs? > > > > I've recently begun a project using Turbine and am quite impressed. I am, > however, currently struggling with how to convince the turbine > user/group/role objects to use 'native' id brokering rather than the > ID_TABLE/idBroker system. It seems to me that this behavior is compiled > into the .jar distributed as part of the tdk (I'm using 2.2rc2) and that > I'm simply stuck and should learn to enjoy using native sequences for my > tables and ID_TABLE for the TURBINE_* classes. > > Is this the case? Obviously not a huge deal; I'm simply curious. > -j > > ------------------------------------------------- > James Diggans > Bioinformatics Programmer > Gene Logic, Inc. > Phone: 301.987.1756 > FAX: 301.987.1701 > > > > > -- > 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]>
