You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Leonardo Quijano Vincenzi (JIRA)" <ta...@jakarta.apache.org> on 2006/04/14 03:13:00 UTC
[jira] Created: (TAPESTRY-912) Add a 'remove' method to
StateObjectPersistenceManager
Add a 'remove' method to StateObjectPersistenceManager
------------------------------------------------------
Key: TAPESTRY-912
URL: http://issues.apache.org/jira/browse/TAPESTRY-912
Project: Tapestry
Type: Improvement
Components: Framework
Versions: 4.0.2
Reporter: Leonardo Quijano Vincenzi
Priority: Minor
Right now there's no official way of destroying a Tapestry ASO, other than injecting the appropiate StateObjectPersistenceManager (such as SessionScopeManager) and calling store(name, null).
In SessionScopeManager's specific case, this causes a NPE. In other implementations there could be similar issues. A "remove" method would be great to actually specify the destruction of a bound ASO, thus freeing system resources. It has other applications too.
--
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-912) Add a 'remove' method to
StateObjectPersistenceManager
Posted by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert updated TAPESTRY-912:
-----------------------------------
Fix Version/s: (was: 4.1.2)
4.1.3
> Add a 'remove' method to StateObjectPersistenceManager
> ------------------------------------------------------
>
> Key: TAPESTRY-912
> URL: https://issues.apache.org/jira/browse/TAPESTRY-912
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0.2
> Reporter: Leonardo Quijano Vincenzi
> Priority: Minor
> Fix For: 4.1.3
>
>
> Right now there's no official way of destroying a Tapestry ASO, other than injecting the appropiate StateObjectPersistenceManager (such as SessionScopeManager) and calling store(name, null).
> In SessionScopeManager's specific case, this causes a NPE. In other implementations there could be similar issues. A "remove" method would be great to actually specify the destruction of a bound ASO, thus freeing system resources. It has other applications too.
--
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-912) Add a 'remove' method to
StateObjectPersistenceManager
Posted by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert updated TAPESTRY-912:
-----------------------------------
Fix Version/s: (was: 4.1.3)
4.1.4
> Add a 'remove' method to StateObjectPersistenceManager
> ------------------------------------------------------
>
> Key: TAPESTRY-912
> URL: https://issues.apache.org/jira/browse/TAPESTRY-912
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0.2
> Reporter: Leonardo Quijano Vincenzi
> Priority: Minor
> Fix For: 4.1.4
>
>
> Right now there's no official way of destroying a Tapestry ASO, other than injecting the appropiate StateObjectPersistenceManager (such as SessionScopeManager) and calling store(name, null).
> In SessionScopeManager's specific case, this causes a NPE. In other implementations there could be similar issues. A "remove" method would be great to actually specify the destruction of a bound ASO, thus freeing system resources. It has other applications too.
--
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-912) Add a 'remove' method to
StateObjectPersistenceManager
Posted by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert updated TAPESTRY-912:
-----------------------------------
Fix Version/s: (was: 4.1.5)
4.1.6
> Add a 'remove' method to StateObjectPersistenceManager
> ------------------------------------------------------
>
> Key: TAPESTRY-912
> URL: https://issues.apache.org/jira/browse/TAPESTRY-912
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0.2
> Reporter: Leonardo Quijano Vincenzi
> Priority: Minor
> Fix For: 4.1.6
>
>
> Right now there's no official way of destroying a Tapestry ASO, other than injecting the appropiate StateObjectPersistenceManager (such as SessionScopeManager) and calling store(name, null).
> In SessionScopeManager's specific case, this causes a NPE. In other implementations there could be similar issues. A "remove" method would be great to actually specify the destruction of a bound ASO, thus freeing system resources. It has other applications too.
--
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-912) Add a 'remove' method to
StateObjectPersistenceManager
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-912?page=all ]
Jesse Kuhnert updated TAPESTRY-912:
-----------------------------------
Fix Version/s: 4.1.2
> Add a 'remove' method to StateObjectPersistenceManager
> ------------------------------------------------------
>
> Key: TAPESTRY-912
> URL: http://issues.apache.org/jira/browse/TAPESTRY-912
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0.2
> Reporter: Leonardo Quijano Vincenzi
> Priority: Minor
> Fix For: 4.1.2
>
>
> Right now there's no official way of destroying a Tapestry ASO, other than injecting the appropiate StateObjectPersistenceManager (such as SessionScopeManager) and calling store(name, null).
> In SessionScopeManager's specific case, this causes a NPE. In other implementations there could be similar issues. A "remove" method would be great to actually specify the destruction of a bound ASO, thus freeing system resources. It has other applications too.
--
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-912) Add a 'remove' method to
StateObjectPersistenceManager
Posted by "Marcus Schulte (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Schulte updated TAPESTRY-912:
------------------------------------
Fix Version/s: (was: 4.1.6)
4.1.7
> Add a 'remove' method to StateObjectPersistenceManager
> ------------------------------------------------------
>
> Key: TAPESTRY-912
> URL: https://issues.apache.org/jira/browse/TAPESTRY-912
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0.2
> Reporter: Leonardo Quijano Vincenzi
> Priority: Minor
> Fix For: 4.1.7
>
>
> Right now there's no official way of destroying a Tapestry ASO, other than injecting the appropiate StateObjectPersistenceManager (such as SessionScopeManager) and calling store(name, null).
> In SessionScopeManager's specific case, this causes a NPE. In other implementations there could be similar issues. A "remove" method would be great to actually specify the destruction of a bound ASO, thus freeing system resources. It has other applications too.
--
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