setupForRequest

[spamsucks <sp...@rhoderunner.com>]

I am porting from T3 to T4.   In T3, I had an engine service that 
implemented the setupForRequest method.  I found some threads about this 
in the list, but they do not apply in my situation.

I was using the setupForRequest method to check the users HttpSession 
for an attribute set there by an earlier filter (sso filter) in which a 
user object is set in the session.  My setupForRequest method would look 
for the user object in the HttpSession and make sure that it was set in 
the tapestry visit object (my tapestry visit object had a 
getUser/setUser method)

I was hoping someone could point out what the correct thing to do under 
T4 would be.  Thanks.

Phillip


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org