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)" <ji...@apache.org> on 2010/09/19 02:16:32 UTC
[jira] Created: (TAP5-1278) Default value for fields is lost at end
of first request
Default value for fields is lost at end of first request
--------------------------------------------------------
Key: TAP5-1278
URL: https://issues.apache.org/jira/browse/TAP5-1278
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.2.0
Reporter: Howard M. Lewis Ship
Priority: Critical
The changes to remove page pooling changed the semantics of initializers to mutable (non-persistent) fields. The fields no longer reset to a saved default value; instead they revert to null or zero.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-1278) Default value for fields is lost at end
of first request
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1278.
--------------------------------------
Resolution: Invalid
Checked the code and this works, must be a logic problem in my application. I'm relieved that I didn't miss something so obvious in the big refactoring.
> Default value for fields is lost at end of first request
> --------------------------------------------------------
>
> Key: TAP5-1278
> URL: https://issues.apache.org/jira/browse/TAP5-1278
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Critical
>
> The changes to remove page pooling changed the semantics of initializers to mutable (non-persistent) fields. The fields no longer reset to a saved default value; instead they revert to null or zero.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-1278) Default value for fields is lost at
end of first request
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1278:
------------------------------------------
Assignee: Howard M. Lewis Ship
> Default value for fields is lost at end of first request
> --------------------------------------------------------
>
> Key: TAP5-1278
> URL: https://issues.apache.org/jira/browse/TAP5-1278
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Critical
>
> The changes to remove page pooling changed the semantics of initializers to mutable (non-persistent) fields. The fields no longer reset to a saved default value; instead they revert to null or zero.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-1278) Default value for fields is lost at
end of first request
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1278:
------------------------------------------
Assignee: Howard M. Lewis Ship
> Default value for fields is lost at end of first request
> --------------------------------------------------------
>
> Key: TAP5-1278
> URL: https://issues.apache.org/jira/browse/TAP5-1278
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Critical
>
> The changes to remove page pooling changed the semantics of initializers to mutable (non-persistent) fields. The fields no longer reset to a saved default value; instead they revert to null or zero.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-1278) Default value for fields is lost at end
of first request
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1278.
--------------------------------------
Resolution: Invalid
Checked the code and this works, must be a logic problem in my application. I'm relieved that I didn't miss something so obvious in the big refactoring.
> Default value for fields is lost at end of first request
> --------------------------------------------------------
>
> Key: TAP5-1278
> URL: https://issues.apache.org/jira/browse/TAP5-1278
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Critical
>
> The changes to remove page pooling changed the semantics of initializers to mutable (non-persistent) fields. The fields no longer reset to a saved default value; instead they revert to null or zero.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.