[
https://issues.apache.org/jira/browse/TAP5-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship updated TAP5-408:
--------------------------------------
Summary: Objects that persist in the session should automatically re-store
themselves into the session at the end of the request (was: Inside Form.java,
any changes to tracker need to call setTracker, to update session object
properly)
This is an expansion of the logic related to Application State Objects in 5.0;
generalized to all objects that are stored in the Session.
There will be a new OptimizedSessionPeristentObject interface, and a
@ImmutableSessionPersistedObject annotation.
> Objects that persist in the session should automatically re-store themselves
> into the session at the end of the request
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-408
> URL: https://issues.apache.org/jira/browse/TAP5-408
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.0, 5.1, 5.0.15, 5.0.16, 5.0.17, 5.0.18
> Reporter: Fernando
> Assignee: Howard M. Lewis Ship
> Priority: Critical
> Attachments: form-session.diff
>
>
> I talked about this on the mailing list. HttpSession objects have a
> requirement that if you dirty an object assigned to it, you have to call
> setAttribute again, to tell the app server the object has been modified.
> Most of the code within Form.java does this properly ( whenever the tracker
> is modified, it calls setTracker, or _tracker = tracker, etc ).
> It missed one spot, and this is a very small patch to fix it.
--
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]
