Seam 2.1 issue: httpServletRequest null within a Create-method

[toby.tobias.hill.gmail.com]

I have two factories (as described in HowCanIAccessTheHttpServletRequestOrSessionDirectly):

<factory name="httpRequest"
  value="#{facesContext.externalContext.request}"
  auto-create="true"/>

<factory name="httpSession"
  value="#{facesContext.externalContext.request.session}"
  auto-create="true"/>

They are accessed from a @Create-annotated method (essentially to deal with some cookie-values when a session starts). This has worked fine in seam 2.0.x but unfortunately evaluates to null in 2.1.0.GA.

Possibly this problem is related to my other posting / jira, but now it seems that the JBoss case behaves as bad as the SeamTest case.

[toby.tobias.hill.gmail.com]

To be precise: It is really the FacesContext that does not exist at the time when the @Create-annotated method on a session scoped component is started (@Startup).

[tazman]

As I wrote in your other topic previously, this doesn't work since Seam 2.1.0.CR1 either:

@Name("sessionStartup")
@Scope(ScopeType.SESSION)
@Startup
public class SessionStartup {
         @In FacesContext facesContext;
        ...

facesContext is always null!

[toby.tobias.hill.gmail.com]

Nice to know that I am not alone then. :)

Well, I managed to workaround it for now:
A HttpFilter picks up the incoming request and response objects and store those on static ThreadLocals. Where I need them (at startup of the mentioned component for instance) I just fetch them from this structure.

Ugly, but works.

[tazman]

Funny that I was thinking about to implement the same workaround as yours, using filters and ThreadLocals :-)

[yahawari]

i ran into the same problem ( Seam 2.1.1 and JBOSS AS 4.3). However, my seam component observes the built in org.jboss.seam.security.loginSuccessful event. The function i have tries to access facesContext, which is always null!.

@In FacesContext facesContext;
@Observer("org.jboss.seam.security.loginSuccessful" )
public void func(){ 
 if(facesContext != null){ 
  HttpSession currentSession =(HttpSession)facesContext.getExternalContext().getSession(false);
   currentSession.setMaxInactiveInterval(7200); 
  }
}

i executed a page action and tries to access facesContext. strangely, facesContext is NOT null.

so Component functions that are executed in response to an event do not have access to faces Context i.e. FacesContext.getCurrentInstance().

it makes sense somehow since seam observer functions are not a part of the JSF cycle.

is there another way to access HttpSession, RequestSession in seam applications ??