quintonm 2003/03/21 14:29:36
Modified: xdocs changes.xml
Log:
Added information about the deprecation of User.getPerm(), User.setPerm(), and perm
scope
pull tools. Also added info about the new sessionData pull tool.
Revision Changes Path
1.44 +20 -0 jakarta-turbine-2/xdocs/changes.xml
Index: changes.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-2/xdocs/changes.xml,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- changes.xml 20 Mar 2003 16:42:33 -0000 1.43
+++ changes.xml 21 Mar 2003 22:29:36 -0000 1.44
@@ -113,6 +113,26 @@
<p>
<ul>
<li>
+ A new pull tool is available in the session scope called $sessionData.
+ This tool can be used to store data that will persist for the duration
+ of the session. This should be used instead of the getTemp() and
+ setTemp() methods in TurbineUser.
+ </li>
+ <li>
+ The use of getPerm() and setPerm() methods in Turbine user have been
+ deprecated. See the Extending Turbine User how-to for using additional
+ database columns for storage if you are using the DBSecurityService.
+ You can also switch to the TorqueSecurityService where it is much easier
+ to use additional columns.
+ </li>
+ <li>
+ Perm scope pull tools have been deprecated. If you use these type of
+ tools, you need to switch to authorized scope pull tools. These tools
+ are initialized with a user object. Any state information that you were
+ storing in the tools itself, you will now need to store in the user
+ object.
+ </li>
+ <li>
Turbine used to remove all data from the session before executing
the login action. This no longer happens. Instead, the session
is invalidated before calling to logout action.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
