ViewExpire exception with @ViewScoped

[Marco Noronha]

Guys,

I was trying to make my APP work with Spring and JSF. And make spring take care of the ManagedBean lifecycle.
But as the cool guys from this forum said, I decided to leave that to JSF and use Spring only for other type of beans.

But now, my viewScoped bean gets its viewExpired and nothing works on it. If I change the ManagedBean to "SessionScoped" than every thing
works like a charm.

NOTE: I tested in both JSF implementations! Both throws the same exception!

So, I´ll show you guys the config files:

web

faces-config

<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" 
id="WebApp_ID" version="2.5">

  <display-name>Projeto Olimpio</display-name>
  
  <context-param>
    <param-name>contextConfigLocation</param-name>
    <param-value>/WEB-INF/applicationContext.xml</param-value>
  </context-param>
  
  <context-param>
    <param-name>javax.faces.FACELETS_SKIP_COMMENTS</param-name>
    <param-value>true</param-value>
  </context-param>
  
  <context-param>
    <description>State saving method: 'client' or 'server' (=default). See JSF Specification 2.5.2</description>
    <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
    <param-value>client</param-value>
  </context-param>
  
  <context-param>
    <param-name>javax.servlet.jsp.jstl.fmt.localizationContext</param-name>
    <param-value>resources.application</param-value>
  </context-param>
  
  <listener>
	<listener-class>
  		org.apache.myfaces.webapp.StartupServletContextListener 
	</listener-class>
  </listener>
 
  <listener>
    <listener-class>
		org.springframework.web.context.ContextLoaderListener
	</listener-class>
  </listener>

  <listener>
    <listener-class>
		org.springframework.web.context.request.RequestContextListener
	</listener-class>
  </listener>

  <servlet>
    <servlet-name>facesServlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
  </servlet>

  <servlet-mapping>
    <servlet-name>facesServlet</servlet-name>
    <url-pattern>*.jsf</url-pattern>
  </servlet-mapping>

  <servlet-mapping>
    <servlet-name>facesServlet</servlet-name>
    <url-pattern>*.xhtml</url-pattern>
  </servlet-mapping>

  <context-param>
    <param-name>javax.faces.PROJECT_STAGE</param-name>
    <param-value>Development</param-value>
  </context-param>
</web-app>

<?xml version="1.0" encoding="UTF-8"?>
<faces-config xmlns="http://java.sun.com/xml/ns/javaee"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
   http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd"
        version="2.0">
 
     <lifecycle>
        <phase-listener>br.com.sol7.olimpio.security.AutorizaListener</phase-listener>
    </lifecycle>
    
    <!--  Spring + JSF integration -->
	<application>
 		<el-resolver>
    		    org.springframework.web.jsf.el.SpringBeanFacesELResolver
		</el-resolver>

	 <message-bundle>mensagens</message-bundle>
    
	<resource-bundle>
		<base-name>mensagens</base-name>
		<var>msg</var>
	</resource-bundle>
		
	</application>

 
</faces-config>

Ok... Now I´ll show you the "header" of my ManagedBean.

@ManagedBean(name = "grupoController")
@ViewScoped
public class GrupoController extends BaseController<Grupo, Integer> implements Serializable {

	private static final long serialVersionUID = 8720936424906553983L;

	@ManagedProperty("#{grupoService}")
	private GrupoService grupoService;

	@ManagedProperty("#{messageUtil}")
	private MessageUtil messageUtil;

	@ManagedProperty("#{genericFilterService}")
	private GenericFilterService genericFilterService;

	private static final Logger log = Logger.getLogger(GrupoController.class);
	
	private LazyDataModel<Grupo> lazyModel;
	
	public GrupoController() {
	}

	
	@PostConstruct
	public void init() {
		super.setBaseService(grupoService);
		super.setMessageUtil(messageUtil);
		super.setLog(log);
		super.setEntity(new Grupo());

Just some explanation.. I Have a abstract class representing all methods and stuff.. But, you guys already noticed that! lol
Since I need a default constructor ... I use postConstruct annotation to set the content of the parent class.

Well, I don´t think I need to show you guys the view (xhtml). The first motive is that I created alot of composite components,
so, the 'dirty' code are all encapsulated.

If I need to show, please ask!
Thanks

[Volodymyr Levytskyi]

Hello!

To have my sessio be expired after 30 minutes of doing nothing I have in my web.xml

    <session-config>
        <session-timeout>
            30
        </session-timeout>
        <cookie-config>
            <name>SESSIONID</name>
        </cookie-config>
    </session-config>

To redirect user to index.xhtml when ViewExpiredException occurs I have this

    <error-page>
        <exception-type>javax.faces.application.ViewExpiredException</exception-type>
        <location>/index.xhtml</location>
    </error-page>

[Marco Noronha]

Volodymyr Levytskyi wrote:Hello!

To have my sessio be expired after 30 minutes of doing nothing I have in my web.xml

    <session-config>
        <session-timeout>
            30
        </session-timeout>
        <cookie-config>
            <name>SESSIONID</name>
        </cookie-config>
    </session-config>

To redirect user to index.xhtml when ViewExpiredException occurs I have this

    <error-page>
        <exception-type>javax.faces.application.ViewExpiredException</exception-type>
        <location>/index.xhtml</location>
    </error-page>

thanks for the reply, but that´s not it!

[Tim Holloway]

I think I mentioned this already, but a JSF backing bean isn't a Controller, It's a Model.

Your use of a DynaForm does tend to muddy a lot of things, though, and it's one reason I haven't been able to give more useful answers.

Views should expire any faster in View Scope than in Session Scope. For one thing, I'm virtually certain that View Scope is simply a Session Scope that cleans up after itself.

My suspicion is that you're referencing the View after the View has been initially departed. I would be unsurprised to learn that you've bound the Dynaform to that view and are attempting to employ it after its context has been destroyed by the View Scope clean-up services.

These are just guesses, however. I'm afraid that when I get hit with large code samples this early in the morning, my response is to fall back in my chair and drool.

[Marco Noronha]

lol lol!

I fixed the problem!!
I can´t believe it was just this:

<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xmlns="http://java.sun.com/xml/ns/javaee"
         xmlns:web="http://java.sun.com/xml/ns/javaee 
          http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"     <!-- REMOVED THIS LINE -->
         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
                                         http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
         id="WebApp_ID"
         version="2.5">

and ViewScoped started to work again!
Buttttttttt !!

I found a person that made a framework that was the 2 scopes I needed!
It is "AccessScope".. The managedBean keeps alive if the next page has references to it.
And its working great!! I talked to the person who did it . He said it is a "spring bean" he created
using orchestra conversation scope.. Something like that. I cant give more information because I lack! lol

But it works great! I´m really surprised!
http://code.google.com/p/lindbergframework/

that is the framework .. the module is called "myview"!

Can you give me an opinion about it?