session-scope

I have a custom AuthenticationSuccessHandler. What I want to do is to set some session data within onAuthenticationSuccess method. To store session data I want to use a session-scoped bean, which works fine within any controller. But if I try to retrieve it within onAuthenticationSuccess method, I get an exception: Error creating bean with name 'scopedTarget.sessionData': Scope 'session' is not active for the current thread; My code is: WebApplicationContext context = WebApplicationContextUtils.getRequiredWebApplicationContext(request.getServletContext()); SessionData sessionData = context

I have SessionScoped bean called userSession to keep track of the user ( username, ifLogged, etc). I want to filter some pages and therefore I need to access the bean from the webFilter I created. How do I do that? I looks like its even impossible to import the bean to be potenitally visible. BalusC Under the covers, JSF stores session scoped managed beans as an attribute of the HttpSession with the managed bean name as key. So, provided that you've a @ManagedBean @SessionScoped public class User {} , just this should do inside the doFilter() method: HttpSession session = ((HttpServletRequest)

I have configured JSF 2.1 in my Google App Engine application following the indications at: https://sites.google.com/a/wildstartech.com/adventures-in-java/Java-Platform-Enterprise-Edition/JavaServer-Faces/javaserver-faces-21/configuring-javaserver-faces-21-to-run-on-the-google-app-engine-using-eclipse The application works perfectly when running locally, but the session is lost when deployed at Google App Engine, e.g.: the component values are lost when updating any other component in the page, and the SessionScope backing bean fields are also lost. My web.xml file is: <?xml version="1.0"

I would like to have a session scoped JSF bean with one property that is request (page) scoped. Is it possible at all? No, that's not possible. Managed property injection only happens during creation of the bean. However, when a session scoped bean is been created there is not necessarily a request present and the injected request scoped bean would be invalid in subsequent requests in the remnant of the session. Do it the other way round. E.g. @ManagedBean @SessionScoped public class UserManager { private User current; // ... } and @ManagedBean @RequestScoped public class Login { private

A Singleton can not autowire a SessionBean but a ScopedProxy can. Assuming 100 users have a valid Session at the same time in the same application, how does the ScopedProxy decide what session is meant? I don't think the ScopedProxy is choosing any random session, this would be nonsense in my opinion. How does the ScopedProxy decide what session to use? What if 0 users have a Session? Will a NullPointerException occur? A @Async is a different Thread than the invoking Request-Processing-Thread how to inject the HttpRequest-Context to the Async task? Renat Gilmanov ThreadLocal is pretty much the

I'm trying to use a pattern found on a IceFaces page.(I'm not using IceFaces, using PrimeFaces) In this case I have two beans: UserController and Usermodel On my UserModel I have a instance of UserVO (created by another programmer). On My UserController I have this: @ManagedBean @RequestScoped public class UserController implements Serializable { private static final long serialVersionUID = 1L; private UserBO bo; private UserModel model; public UserController() { bo = new UserBO(); model = new UserModel(); } public void Login() throws IOException { model.setUserVo(bo.executeLogin(model