[
https://issues.apache.org/jira/browse/TAP5-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship updated TAP5-399:
--------------------------------------
Description:
The fix for TAPESTRY-2595 is incomplete: it is based on the class
SessionApplicationStatePersistenceStrategy being registered as an
EndOfRequestListener with the EndOfRequestListenerHub. This is not done, thus
the strategy never gets a chance to locate modified ASOs and re-write them into
the session.
Modified ASOs need to be stored back into the session at the end of the request
to ensure that any changes are propagated to other servers in the cluster.
was:The fix for TAPESTRY-2595 is incomplete: it is based on the class
SessionApplicationStatePersistenceStrategy being registered as an
EndOfRequestListener with the EndOfRequestListenerHub. This is not done, thus
the strategy never gets a chance to locate modified ASOs and re-write them into
the session.
Summary: Modified application state objects are not persisted back to
the session at the end of the request (was: Modified ASO objects are not
persisted back to the session ever)
> Modified application state objects are not persisted back to the session at
> the end of the request
> --------------------------------------------------------------------------------------------------
>
> Key: TAP5-399
> URL: https://issues.apache.org/jira/browse/TAP5-399
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.0, 5.0.17
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Blocker
> Fix For: 5.1.0.0, 5.0.18
>
>
> The fix for TAPESTRY-2595 is incomplete: it is based on the class
> SessionApplicationStatePersistenceStrategy being registered as an
> EndOfRequestListener with the EndOfRequestListenerHub. This is not done,
> thus the strategy never gets a chance to locate modified ASOs and re-write
> them into the session.
> Modified ASOs need to be stored back into the session at the end of the
> request to ensure that any changes are propagated to other servers in the
> cluster.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
