interesting issue with Controller and FacesContext

Posted Wed, 15/07/2009 - 14:08 by oded
, , ,

Hi,

 

Does anyone know why when i try to get FacesContext.getCurrentInstance() inside Controller implemenation function (handleRequest),

the current instance is null?

 

Thanks,

Oded.

 

 

‹ Online pre-configuration of JEE web applications Seam error: javax.faces.application.ViewExpiredException ›

Comments

by arik - 15/07/2009 - 16:59

Can you put some more information?
Like code example of what are you exactly trying to do?
Environment details, what kind of thirdparty are you using?

It might be life cycle issue or thirdparty issue.

by oded - 16/07/2009 - 12:10 
we are having a jsf / facelets and acegi spring security..
just a regular controller defined in the web.xml
<servlet-mapping>
	<servlet-name>ssoLogin</servlet-name>
	<url-pattern>/ssoLogin/*</url-pattern>
</servlet-mapping>
<servlet>
	<servlet-name>ssoLogin</servlet-name>
	<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
	<load-on-startup>2</load-on-startup>
</servlet>
and defined in ssoLogin-servlet.xml
<bean name="/login" class="com.XXX.XXX.XXX.SSOController" />
and as I mentioned I'm trying to get the current instance which is null --> FacesContext.getCurrentInstance().getExternalContext().getContext()
Cheers.

by shlomo - 16/07/2009 - 12:16

I am not a Spring user or advocate (I am using Seam) but I think your request isn't in a JSF context. It would be beneficial to know why you need the FacesContext in your bean/controller and what you are using it for.

Any way, these might be helpful:

http://cagataycivici.wordpress.com/2005/12/25/integrating_jsf_and_spring/

http://blogs.steeplesoft.com/facesutil-a-missing-yet-important-piece/

http://www.thoughtsabout.net/blog/archives/000033.html

by arik - 16/07/2009 - 13:42

Yeah it looks like you need the third link Shlomo referenced.

by yossis - 16/07/2009 - 14:33

It is !

by oded - 16/07/2009 - 14:58 
I need to initial a jsf bean from that spring controller and then to navigate.
yes, it makes sense, this controller is a Spring MVC and i want it to work on a Spring Web Flow, 
in other words, this controller is not going through the jsf-faces servlet?
if so, how can I make a spring controller work with jsf ?

by oded - 16/07/2009 - 15:03 
yes, the third link really might help :)
"because a filter is running before a Faces servlet the context hasn't been set up for this request"
Thanks, guys.

by yossis - 16/07/2009 - 17:02

it is working, i checked it . with the same environment like yours off course :)

by oded - 16/07/2009 - 17:37 
yes it is working (indeed a neat work-around :) ), 
but , a better way dealling with this issue would be using @controller instead of implementing controller(MVC),
having jsf/spring faces abilities and mvc together. 
in this way the controller is in the same scope (@Autowired can be used and faces context is alive...)