[
https://issues.apache.org/jira/browse/TAPESTRY-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship updated TAPESTRY-1991:
-------------------------------------------
Summary: It should be easier to access an Application State Object without
forcing its creation (was: It should be easy to initialize an ASO to null)
This will work great the with property expression ?. operator, i.e., <t:if
test="user?.loggedIn"> ... </t:iif>
> It should be easier to access an Application State Object without forcing its
> creation
> --------------------------------------------------------------------------------------
>
> 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
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.0.8
>
>
> 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]
