I think Chris is refering to Application State Objects, right Chris ?
Anyway, i don't think that what you are saying is possible(although i
never really tried doing that). What i usually do for implementing a
functionality similar to what you want is adding a property "user" to
the visit ASO. Before the user logs in that property is always null so
you can check if a user is logged by a /getVisit().getUser() == null
/statement. You can simplofy this even further by implementing in you
base class a method like:
boolean isUserLogged()
{
return getVisit().getUser() != null;
}
Hope this helped.
Cheers
Hugo
Erik Hatcher wrote:
What is an "ASO"?
On Jun 15, 2005, at 1:03 AM, Chris Conrad wrote:
I was wondering if there is a way to specify that my ASOs should be
set to null by default instead of Tapestry creating a new instance?
I'd like to use an ASO to store logged in user information. If
getUser() returns null then I know the user isn't logged in.
Instead I need to do getUser.getId() == 0 which works, but doesn't
feel as clean as doing a null check.
--Chris
---------------------------------------------------------------------
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]
