Thanks a lot that works great :-)
On 3/16/07, DJ Gredler [EMAIL PROTECTED] wrote:
I haven't looked into this stuff yet, but if I were dealing with it I'd
probably just make a new ApplicationState class with a user property that
I
could set at will, and let Tapestry instantiate the
I am trying to store a user as an ASO. I am able to set the user, but when I
want to log out, I figured the right way to do it was to just set the user
ASO to null. I believe this works fine, just that now when I chcek to see if
the user is null or not, as expected, the application state manager
I haven't looked into this stuff yet, but if I were dealing with it I'd
probably just make a new ApplicationState class with a user property that I
could set at will, and let Tapestry instantiate the ApplicationState
whenever it wants to. Of course, once T5 supports ASO flags, you'd want to
start
()
{
public MyState create()
{
return new MyState(new Date());
}
};
configuration.add(MyState.class, new
ApplicationStateContribution(session, creator));
}
--
View this message in context:
http://www.nabble.com/-T5-Question-on-ASO-configuration-tf3399851.html
://www.nabble.com/-T5-Question-on-ASO-configuration-tf3399851.html#a9467437
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
()
{
return new MyState(new Date());
}
};
configuration.add(MyState.class, new
ApplicationStateContribution(session, creator));
}
--
View this message in context:
http://www.nabble.com/-T5-Question-on-ASO-configuration-tf3399851.html#a9467437
Sent from the Tapestry
