[
https://issues.apache.org/jira/browse/TAP5-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788198#action_12788198
]
Howard M. Lewis Ship commented on TAP5-836:
-------------------------------------------
I can't think of any place in Tapestry's code where an EventContext would be
stored in the session.
However, it is not an uncommon pattern to intercept requests for pages that
require non-anonymous access, redirect through a login page and process, and
then continue back to the original request. That's the most likely culprit.
I've implemented this pattern myself, and just extracted the URL context values
as strings to store them (inside another object) inside the session.
> URLEventContext is not Serializable - prevents Tapestry use in a Cluster
> ------------------------------------------------------------------------
>
> Key: TAP5-836
> URL: https://issues.apache.org/jira/browse/TAP5-836
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Environment: CentOS 5.3, Java 1.6.0_14-b08, Tomcat 5.5.27
> Reporter: David Rees
> Priority: Critical
>
> I have a Tapestry application which I am trying to use in a Tomcat cluster.
> Tomcat uses Object Input/Output Streams to replicate session data, which
> requires that all objects added to a Session implement Serializable.
> In Tapestry 5.0.18 (and all later versions from what I can tell from browsing
> source), org.apache.tapestry5.internal.URLEventContext does not implement
> Serializable which prevents us from using Tapestry in a cluster.
> Unfortunately, this means that when we have to deploy a new version of our
> application, we have to forcibly log everyone out disrupting service.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
