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)" <de...@tapestry.apache.org> on 2008/01/20 23:24:35 UTC

[jira] Assigned: (TAPESTRY-1991) It should be easy to initialize an ASO to null

     [ https://issues.apache.org/jira/browse/TAPESTRY-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAPESTRY-1991:
----------------------------------------------

    Assignee: Howard M. Lewis Ship

> 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
>            Assignee: Howard M. Lewis Ship
>            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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org