svn commit: r1149673 - /shiro/trunk/RELEASE-NOTES

[lh...@apache.org]

Author: lhazlewood
Date: Fri Jul 22 18:03:06 2011
New Revision: 1149673

URL: http://svn.apache.org/viewvc?rev=1149673&view=rev
Log:
Updated Release Notes to indicate ServletContainerSessionManager change

Modified:
    shiro/trunk/RELEASE-NOTES

Modified: shiro/trunk/RELEASE-NOTES
URL: http://svn.apache.org/viewvc/shiro/trunk/RELEASE-NOTES?rev=1149673&r1=1149672&r2=1149673&view=diff
==============================================================================
--- shiro/trunk/RELEASE-NOTES (original)
+++ shiro/trunk/RELEASE-NOTES Fri Jul 22 18:03:06 2011
@@ -36,6 +36,18 @@ Backwards Incompatible Changes
   If you overrode this method in Shiro 1.0 or 1.2, please look at the new
   org.apache.shiro.mgt.DefaultSubjectDAO implementation, which performs compatible logic.
 
+- The org.apache.shiro.web.session.mgt.ServletContainerSessionManager implementation
+  (enabled by default for all web applications) no longer subclasses
+  org.apache.shiro.session.mgt.AbstractSessionManager.  AbstractSessionManager existed
+  originally to consolidate a 'globalSessionTimeout' configuration property for
+  subclasses.  However, the ServletContainerSessionManager has been changed to always
+  reflect the session configuration from web.xml (per its namesake).  Because web.xml
+  is the definitive source for session timeout configuration, the 'extends' clause
+  was removed to avoid configuration confusion: if someone attempted to configure
+  'globalSessionTimeout' on a ServletContainerSessionManager instance, it would never
+  be honored.  It was better to remove the extends clause to ensure that any
+  such configuration would fail fast when Shiro starts up to reflect the invalid config.
+
 Potential Breaking Changes
 --------------------------------
 - The org.apache.shiro.web.filter.mgt.FilterChainManager class's