Yes, the default semantics is that it will only create the ASO instance once you try to access it. Still, it seems to me that many times this semantics doesn't really make sense, in the cases where the ASO being null has a meaning. The simplest case being for example when you want to keep as an ASO the logged user.

I know the docs say that you can keep a boolean value keeping score if the ASO was actually created or not, but to me this seems to go against everything T5 stands for. This kind of thing really should be easy.

Davor Hrg wrote:
I haven't checked it in practice, I belived what docs say:
http://tapestry.formos.com/nightly/tapestry5/tapestry-core/guide/appstate.html

I think the object will not be created if you do not try to access the variable.

Davor Hrg

On Dec 20, 2007 4:36 PM, Hugo Palma (JIRA) <[email protected]> wrote:
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]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to