Well, I've just started evaluating 2.3 - we're in the process of doing a rather large migration (more of a proof of concept first) of an ASP application to a fully-fledged Tomcat/Turbine/Velocity JSP application! I hope it goes relatively smoothly. I'm sure I'll have questions for this list over the next few weeks.
Cheers, -Matt -----Original Message----- From: Brian Lawler [mailto:[EMAIL PROTECTED] Sent: Wednesday, 4 February 2004 2:11 PM To: Turbine Users List Subject: Re: TURBINE_USER using a native idMethod... Scott- Thanks for the quick reply! I knew that there must have been something to address what has long been a popular list topic. I am currently digging into that service and the rest of our code to get this upgrade finished. The exercise of going from our tweaked up and vastly outdated 2.2 version into 2.3 has also required that I take a good hard look at our security implementation from top to bottom. I am currently reviewing the "User" interface and am forced to wonder, why does it not implement getId()? Is there some historical reason to have overlooked this method? For my architecture layer above Turbine I end up needing to create a child Interface whose job it is to add that method which is, of course, no big deal. Just curious as to whether there is any history I am missing out on... Thanks again for all the great work! T2.3 is a great improvement of T2.2 from what I have seen so far - just have to plow through all of these upgrade issues. Out of curiosity, am I the only one on this list who is still stuck on T2.2? I am curious as to whether a compilation of the issues I am encountering would be helpful or if this is all just old news... -Brian On Tuesday, February 3, 2004, at 02:12 PM, Scott Eade wrote: > Brian Lawler wrote: > >> Seems like many of the online docs and questions in the past have >> dealt with extending TURBINE_USER, but I can't find any info on the >> preferred method of changing the idMethod. We need to use >> autoincrement for generating this id, and the way I did this in >> Turbine 2.2 was to actually change the TurbineMapBuilder.java file in >> the turbine jar (gasp!) It seems like T2.3 is trying to address the >> user generated Torque approach, so is there now a better way to do >> this or should I continue polluting my jar file with tribe.net >> specific extensions? > > > In T2.3 you should use the Torque Security Service > (http://jakarta.apache.org/turbine/turbine-2.3/services/torque- > security-service.html). You generate the underlying OM for using > Torque and if you set the idMethod to native it works well. > > Scott > > -- > Scott Eade > Backstage Technologies Pty. Ltd. > http://www.backstagetech.com.au > > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
