I don't have the time to go through your setup in the moment - but I can tell you that the back button problem has been solved even with server side state saving in the latest nightly builds.
So you can go to server side state saving and still use the back button! regards, Martin On 10/22/05, Julián García <[EMAIL PROTECTED]> wrote: > > In fact I was using a <context-param> for javax.faces.CONFIG_FILES, > despite the name was faces-config, however, the problem still persists, > when I get rid of the context param. > > As I already mentioned, the problem is present whenever I use client > state saving. Using server saving solves it, but since my users are used > to use the back button that is not an option for me. > > > Please help, I am really in a hurry.... > > My web.xml looks like this: > > <?xml version="1.0"?> > <!DOCTYPE web-app PUBLIC > "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" > "http://java.sun.com/dtd/web-app_2_3.dtd";> > > <web-app> > <display-name>Sofia Cartera</display-name> > <description>Sofia Cartera</description> > > <context-param> > <param-name>javax.faces.STATE_SAVING_METHOD</param-name> > <param-value>server</param-value> > </context-param> > > <context-param> > <param-name>org.apache.myfaces.ALLOW_JAVASCRIPT</param-name> > <param-value>true</param-value> > </context-param> > > <context-param> > <param-name>org.apache.myfaces.PRETTY_HTML</param-name> > <param-value>true</param-value> > </context-param> > > <context-param> > <param-name>org.apache.myfaces.DETECT_JAVASCRIPT</param-name> > <param-value>false</param-value> > </context-param> > > <context-param> > <param-name>org.apache.myfaces.AUTO_SCROLL</param-name> > <param-value>true</param-value> > <description> > </description> > </context-param> > > <context-param> > <param-name>contextConfigLocation</param-name> > <param-value>/WEB-INF/classes/sofiaContext.xml</param-value> > </context-param> > > <!--Soporte tiles de myfaces--> > <context-param> > <param-name>tiles-definitions</param-name> > <param-value>/WEB-INF/tiles.xml</param-value> > </context-param> > > > <!--Filtro Autenticacion Sencilla--> > <filter> > <filter-name>authenticationFilter</filter-name> > <filter-class> > co.com.atenaerp.authentication.AuthenticationFilter > </filter-class> > </filter> > > > <!--Filtro para mantener la sesion de hibernate y habilitar lazy > fetching--> > <filter> > <filter-name>hibernateFilter</filter-name> > <filter-class> > > org.springframework.orm.hibernate.support.OpenSessionInViewFilter > </filter-class> > <init-param> > <param-name>singleSession</param-name> > <param-value>true</param-value> > </init-param> > </filter> > > <filter> > <filter-name>extensionsFilter</filter-name> > > <filter-class>org.apache.myfaces.component.html.util.ExtensionsFilter</filter-class> > <init-param> > <param-name>uploadMaxFileSize</param-name> > <param-value>100m</param-value> > </init-param> > <init-param> > <param-name>uploadThresholdSize</param-name> > <param-value>100k</param-value> > </init-param> > </filter> > > > <filter-mapping> > <filter-name>extensionsFilter</filter-name> > <url-pattern>*.jsf</url-pattern> > </filter-mapping> > > <filter-mapping> > <filter-name>authenticationFilter</filter-name> > <url-pattern>/*</url-pattern> > </filter-mapping> > > <filter-mapping> > <filter-name>hibernateFilter</filter-name> > <url-pattern>/*</url-pattern> > </filter-mapping> > > > <filter-mapping> > <filter-name>extensionsFilter</filter-name> > <url-pattern>/faces/*</url-pattern> > </filter-mapping> > > <!--Listener para contexto de spring--> > <listener> > <listener-class> > org.springframework.web.context.ContextLoaderListener > </listener-class> > </listener> > > <!--Listener para contexto de JSF--> > <listener> > <listener-class> > > org.apache.myfaces.webapp.StartupServletContextListener > </listener-class> > <!--org.apache.myfaces.webapp.StartupServletContextListener--> > </listener> > > <!-- Faces Servlet --> > <servlet> > <servlet-name>Faces Servlet</servlet-name> > <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> > </servlet> > > <servlet-mapping> > <servlet-name>Faces Servlet</servlet-name> > <url-pattern>*.jsf</url-pattern> > </servlet-mapping> > > <!--Tiempo de validez de la sesión en minutos--> > <session-config> > <session-timeout>15</session-timeout> > </session-config> > > <!--Listado de páginas de bienvenida--> > <welcome-file-list> > <welcome-file>index.jsp</welcome-file> > </welcome-file-list> > > <error-page> > <error-code>404</error-code> > <location>/error.jsp</location> > </error-page> > > </web-app> > > > Thanks. > > Julian > > > Kevin Hale Boyes wrote: > > Check your web.xml file to see if you're including faces-config.xml > > if defined in the <context-param> for javax.faces.CONFIG_FILES. > > > > faces-config.xml is automatically loaded by JSF so if you've specified > > in the context-param then it is loaded twice. This causes some actions > > to be called twice. At least, this is how my brain remembers a similar > > problem from a few months ago. > > > > K. > > > > > > -----Original Message----- > > From: Julián García [mailto:[EMAIL PROTECTED] > > Sent: Thursday, October 20, 2005 4:41 PM > > To: MyFaces Discussion > > Subject: Action called twice > > > > Although I have not discovered a pattern yet, some of my action methods are > > being called twice on invocation. Is this a known issue? I am strugling > > with this..... > > > > Julian > > > > > > -- http://www.irian.at Your JSF powerhouse - JSF Trainings in English and German
