RE: Still facing problems in accessing the beans in scopes other than flow scope.

[jeremyg484]

Is there any other scope (like request) where the bean life cycle will be managed by spring and the bean instance won't be available after the authentication action is over. I want to know more about the scope similar to request here.

In this particular instance then, why not just use request scope? It seems it would fulfill your needs exactly.

-Jeremy

[shashi]

Hi Jeremy,

Thanks for your reply.

To use a bean in request scope, I think I don't have to define any scope for the bean, the way mentioned below:

<bean id="login" class="MyLoginClass"/>

and access the bean in the jsp as

<h:inputText id="loginid" value="#{login.id}"/>
<h:inputText id="password" value="#{login.password}"/>

However I still get the bean as null in the request scope. Is there anything I am doing here?

Thanks once more for your help,
Shashi

[jeremyg484]

You need to explicitly specify request scope. The config you show will use the Spring default of singleton scope, which is definitely not what you want.

Keep in mind that http request scope and flow request scope (that accessible through RequestContext) are two different things. When you define your bean as:

<bean id="login" class="MyLoginClass" scope="request"/>

you are defining it in http request scope. If you are trying to then manipulate it from your intermediary action, the cleanest and easiest thing is to use Spring's dependency injection. On the other hand, if you for some reason defined the bean as a JSF managed bean in request scope, you could use the same code as I described before where you try to access the bean using JSF's variable resolution mechanism.

-Jeremy