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...
The User interface most likely does not implement getId() because depending on the underlying implementation there may not be an Id at all (I think this may be the case for LDAP). If you use the Torque Security Service and plan on sticking with it it is relatively easy to obtain the id bu casting to the underlying user class.
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...
T2.3 is indeed a great improvement over T2.2 and the developers have my thanks also. Make sure you check the migration document (http://jakarta.apache.org/turbine/turbine-2.3/howto/migrate-from-2_2-howto.html). I am sure the list would be grateful for coverage of issues not covered there (I would imagine there are still quite a number of people back on T2.2).
BTW: If you use intake extensively I recommend that you build yourself a turbine-2.3.1-dev.jar from the TURBINE_2_3 branch of cvs.
Regards,
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]
