[
https://issues.apache.org/jira/browse/TAPESTRY-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555943#action_12555943
]
Howard M. Lewis Ship commented on TAPESTRY-1991:
------------------------------------------------
Fair enough .... I'm just in a state of trying to get T5 into a stable,
releasable state, so I'm aggressively looking to avoid more work. We can leave
this open, but it probably won't be implemented for the final release, and can
go into a follow-on release. The change in question would be backwards
compatble (the create attribute would default to true).
> It should be easy to initialize an ASO to null
> ----------------------------------------------
>
> Key: TAPESTRY-1991
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1991
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 5.0.6
> Reporter: Hugo Palma
> Priority: Minor
>
> By default an ASO is never null. It's automatically created using the ASO
> class default constructor.
> It's many times needed to have the null value in an ASO, for example if i
> want to keep the logged in user in an ASO.
> Right now we can do this by contributing a new ApplicationStateCreator to the
> ApplicationStateManager but it seems to me that should be as easy as
> providing a parameter to the @ApplicationState indicating that you don't want
> it to be automatically initialized.
--
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]
