Managed session bean in servlet filter

Question

Hi,
Is there a way to get hold of a managed bean with session scope in a servlet filter? The code below throws an error due to the fact that the faces context is null.
FacesContext facesContext = FacesContext.getCurrentInstance();
System.out.println("facesContext: " + facesContext); // shows that facesContext is null
ApplicationFactory appFactory = ApplicationFactory)FactoryFinder.getFactory(FactoryFinder.APPLICATION_FACTORY);
Application app = appFactory.getApplication();
Object obj = app.createValueBinding("user").getValue(facesContext); //throws the error due to the null parameter
Object obj2 = app.createValueBinding("user"); //results in a valid ValueBindingHere is the faces-config snippet for the managed bean:
<managed-bean>
    <managed-bean-name>user</managed-bean-name>
    <managed-bean-class>biz.libereco.skemo.info.asl.beans.User</managed-bean-class>
    <managed-bean-scope>session</managed-bean-scope>
</managed-bean>For the record, I am using JSF 1.0 Final.
Thank you,
Marcel

Answer 1

wynton_0 wrote:
Yes, there is a way to get hold of a managed bean with session scope in a servlet filter.
See here:
[http://wiki.apache.org/myfaces/AccessFacesContextFromServlet]
and here:
[how to access faces context and backing beans in a servlet filter|http://www.thoughtsabout.net/blog/archives/000033.html]
This makes no utter sense. A JSF session scoped managed bean is under the hood just put as a HttpSession attribute with the managed bean name as key. Guess what, you can just access the HttpSession in Filter by ((HttpServletRequest) request).getSession() and then just call getAttribute() on it. If it isn't there yet, then just do a setAttribute() with a new instance.
After I get User bean in my Servlet filter, I populate value to this bean, for example:
user.setLanguage(request.getParameter("locale"));
The User bean is in session scope. The User bean's language attribute suppose to be same in the whole session scope, but later on, I got null. My question is:
how to keep this value in session scope?The the session was apparently invalidated/renewed or you manually removed the bean or replaced it by null.
In the future, please don't resurrect old topics, just start a new topic for each independent problem/question.