You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Andrew Robinson (JIRA)" <de...@myfaces.apache.org> on 2011/05/02 23:25:03 UTC
[jira] [Created] (TRINIDAD-2096) Change when the UIXCollection adds
its component context change
Change when the UIXCollection adds its component context change
---------------------------------------------------------------
Key: TRINIDAD-2096
URL: https://issues.apache.org/jira/browse/TRINIDAD-2096
Project: MyFaces Trinidad
Issue Type: Improvement
Components: Components
Affects Versions: 2.0.0-beta-1
Reporter: Andrew Robinson
Assignee: Andrew Robinson
During my initial authoring of the UIXCollection component context change, it was possible for code that did not reset the row key back to its original value, to leave a context change dangling off of the stack. This causes issue with other components that use context changes.
I am changing the code to only use the component context change when the component is being processed. This way it is sure to be cleaned up as a try/finally block would be feasible.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TRINIDAD-2096) Change when the UIXCollection
adds its component context change
Posted by "Andrew Robinson (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Robinson resolved TRINIDAD-2096.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.1
> Change when the UIXCollection adds its component context change
> ---------------------------------------------------------------
>
> Key: TRINIDAD-2096
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2096
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Components: Components
> Affects Versions: 2.0.0-beta-1
> Reporter: Andrew Robinson
> Assignee: Andrew Robinson
> Fix For: 2.0.1
>
>
> During my initial authoring of the UIXCollection component context change, it was possible for code that did not reset the row key back to its original value, to leave a context change dangling off of the stack. This causes issue with other components that use context changes.
> I am changing the code to only use the component context change when the component is being processed. This way it is sure to be cleaned up as a try/finally block would be feasible.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira