Re: Critique implementation of managed bean access

[Mark]

Ray Clark wrote:
Mark:
Maybe you should try using the x:saveState tag.  In
the Struts apps that we have at work, we have a user
object that gets created in a filter and put in to
session.  Then the app accesses the user object when
it needs to.  Well, I'm at home trying to mimick some
of the things that we do as a proof of concept.  So I
have a login page that has a login request scope bean.
Then when the user types in a valid user id and
password it builds the user object and puts it in
session.  The login page works fine if the login bean
had session scope but didn't work if it was request
scope.  Following the advice from a couple of days ago
on this list I tried the x:saveState tag and poof, it
works like a champ.  Here is the tag that I have for
the request scope login bean on the login page.
<x:saveState id="userBean" value="#{user}"/>
It sounds like this might be what you are looking for.
Ray
 

Thanks for the advice. I tried it but it didn't work.  I may be doing 
something wrong but I'm not sure.

Would it make any difference that the value I need to save is initially 
null and is set via an action listener?

thanks,
-Mark