You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org> on 2005/05/04 22:43:05 UTC
[jira] Created: (TAPESTRY-312) lifecycle of session
<bean> lifecycle of session
---------------------------
Key: TAPESTRY-312
URL: http://issues.apache.org/jira/browse/TAPESTRY-312
Project: Tapestry
Type: Improvement
Components: Framework
Versions: 4.0
Reporter: Howard M. Lewis Ship
Fix For: 4.0
It would be quite cool if you could define a bean with a lifecycle of "session" and Tapestry could take care of obtaining it from the session (as needed) and persisting it back to the session at the end of the requesty cycle, much like an application state object.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Updated: (TAPESTRY-312) lifecycle of session
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-312?page=all ]
Jesse Kuhnert updated TAPESTRY-312:
-----------------------------------
Fix Version/s: 4.1.2
(was: 4.1.1)
> <bean> lifecycle of session
> ---------------------------
>
> Key: TAPESTRY-312
> URL: http://issues.apache.org/jira/browse/TAPESTRY-312
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Fix For: 4.1.2
>
>
> It would be quite cool if you could define a bean with a lifecycle of "session" and Tapestry could take care of obtaining it from the session (as needed) and persisting it back to the session at the end of the requesty cycle, much like an application state object.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-312) lifecycle of session
Posted by "Peter Ertl (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-312?page=comments#action_12322584 ]
Peter Ertl commented on TAPESTRY-312:
-------------------------------------
yes, please!
this would be especially helpful if somebody uses the post-redirect-get pattern (a personal favourite as
it eliminates some browser-specific annoyances). that way the state of the form delegate could be preserved easily
so error messages do not disappear after the redirect.
> <bean> lifecycle of session
> ---------------------------
>
> Key: TAPESTRY-312
> URL: http://issues.apache.org/jira/browse/TAPESTRY-312
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Fix For: 4.0
>
> It would be quite cool if you could define a bean with a lifecycle of "session" and Tapestry could take care of obtaining it from the session (as needed) and persisting it back to the session at the end of the requesty cycle, much like an application state object.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Updated: (TAPESTRY-312) lifecycle of session
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-312?page=all ]
Jesse Kuhnert updated TAPESTRY-312:
-----------------------------------
Fix Version: 4.0.2
(was: 4.0)
Environment:
> <bean> lifecycle of session
> ---------------------------
>
> Key: TAPESTRY-312
> URL: http://issues.apache.org/jira/browse/TAPESTRY-312
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Fix For: 4.0.2
>
> It would be quite cool if you could define a bean with a lifecycle of "session" and Tapestry could take care of obtaining it from the session (as needed) and persisting it back to the session at the end of the requesty cycle, much like an application state object.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Updated: (TAPESTRY-312) lifecycle of session
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert updated TAPESTRY-312:
-----------------------------------
Fix Version/s: (was: 4.1.2)
4.2
> <bean> lifecycle of session
> ---------------------------
>
> Key: TAPESTRY-312
> URL: https://issues.apache.org/jira/browse/TAPESTRY-312
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Fix For: 4.2
>
>
> It would be quite cool if you could define a bean with a lifecycle of "session" and Tapestry could take care of obtaining it from the session (as needed) and persisting it back to the session at the end of the requesty cycle, much like an application state object.
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-312) lifecycle of session
Posted by "Andreas Andreou (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-312?page=all ]
Andreas Andreou updated TAPESTRY-312:
-------------------------------------
Fix Version: 4.0.3
(was: 4.0.2)
> <bean> lifecycle of session
> ---------------------------
>
> Key: TAPESTRY-312
> URL: http://issues.apache.org/jira/browse/TAPESTRY-312
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Fix For: 4.0.3
>
> It would be quite cool if you could define a bean with a lifecycle of "session" and Tapestry could take care of obtaining it from the session (as needed) and persisting it back to the session at the end of the requesty cycle, much like an application state object.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Updated: (TAPESTRY-312) lifecycle of session
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-312?page=all ]
Jesse Kuhnert updated TAPESTRY-312:
-----------------------------------
Fix Version: 4.1
(was: 4.0.3)
> <bean> lifecycle of session
> ---------------------------
>
> Key: TAPESTRY-312
> URL: http://issues.apache.org/jira/browse/TAPESTRY-312
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Fix For: 4.1
>
> It would be quite cool if you could define a bean with a lifecycle of "session" and Tapestry could take care of obtaining it from the session (as needed) and persisting it back to the session at the end of the requesty cycle, much like an application state object.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-312) lifecycle of session
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-312?page=all ]
Jesse Kuhnert updated TAPESTRY-312:
-----------------------------------
Fix Version/s: 4.1.1
(was: 4.1)
> <bean> lifecycle of session
> ---------------------------
>
> Key: TAPESTRY-312
> URL: http://issues.apache.org/jira/browse/TAPESTRY-312
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Fix For: 4.1.1
>
>
> It would be quite cool if you could define a bean with a lifecycle of "session" and Tapestry could take care of obtaining it from the session (as needed) and persisting it back to the session at the end of the requesty cycle, much like an application state object.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org