Author: hlship
Date: Wed Dec 9 18:07:00 2009
New Revision: 888898
URL: http://svn.apache.org/viewvc?rev=888898&view=rev
Log:
TAP5-834: BaseOptimizedSessionPersistedObject does not work correctly with
Tomcat & Jetty
Modified:
tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/SessionImpl.java
Modified:
tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/SessionImpl.java
URL:
http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/SessionImpl.java?rev=888898&r1=888897&r2=888898&view=diff
==============================================================================
---
tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/SessionImpl.java
(original)
+++
tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/SessionImpl.java
Wed Dec 9 18:07:00 2009
@@ -127,7 +127,7 @@
if (analyzer.isDirty(attributeValue))
{
- // TAP5-384: Jetty & Tomcat work by object identity, will not
update the attribute
+ // TAP5-834: Jetty & Tomcat work by object identity, will not
update the attribute
// and fire the session binding event unless there's a real
change. So we set the
// attribute to null and then to the new value and that should
force the necessary
// notification.
