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]
