tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Moved: (TAP5-836) URLEventContext is not Serializable - prevents Tapestry use in a Cluster
Date Thu, 03 Sep 2009 18:03:57 GMT

     [ https://issues.apache.org/jira/browse/TAP5-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship moved TAPESTRY-2743 to TAP5-836:
-----------------------------------------------------

          Component/s:     (was: tapestry-core)
    Affects Version/s:     (was: unspecified)
                  Key: TAP5-836  (was: TAPESTRY-2743)
              Project: Tapestry 5  (was: Tapestry)

> 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
>         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.


Mime
View raw message