Hi, don't you have anobody idea why url is laggin one step behind the actual url of the application? For example the app is in /page1.jsf with navigation control pointing to /page2.jsf. After firing the control the navigation properly handles the request and /page2.jsf is displayed, however, in the brower (and also in navigation handler) I'm getting /page1.jsf. The proper url is shown after another step.
I'm using myfaces 1.1.1, web.xml and faces-config in the attachment. Thanks jan
<?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> <context-param> <param-name>javax.faces.CONFIG_FILES</param-name> <param-value> <!--/WEB-INF/examples-config.xml,--> /WEB-INF/faces-config.xml, /META-INF/faces-zcomp.xml, /META-INF/components.xml </param-value> <description> Comma separated list of URIs of (additional) faces config files. (e.g. /WEB-INF/my-config.xml) See JSF 1.0 PRD2, 10.3.2 </description> </context-param> <context-param> <param-name>javax.faces.STATE_SAVING_METHOD</param-name> <param-value>client</param-value> <description> State saving method: "client" or "server" (= default) See JSF Specification 2.5.2 </description> </context-param> <context-param> <param-name>org.apache.myfaces.ALLOW_JAVASCRIPT</param-name> <param-value>true</param-value> <description> This parameter tells MyFaces if javascript code should be allowed in the rendered HTML output. If javascript is allowed, command_link anchors will have javascript code that submits the corresponding form. If javascript is not allowed, the state saving info and nested parameters will be added as url parameters. Default: "true" </description> </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.PRETTY_HTML</param-name> <param-value>true</param-value> <description> If true, rendered HTML code will be formatted, so that it is "human readable". i.e. additional line separators and whitespace will be written, that do not influence the HTML code. Default: "true" </description> </context-param> <context-param> <param-name>org.apache.myfaces.AUTO_SCROLL</param-name> <param-value>true</param-value> <description> If true, a javascript function will be rendered that is able to restore the former vertical scroll on every request. Convenient feature if you have pages with long lists and you do not want the browser page to always jump to the top if you trigger a link or button action that stays on the same page. Default: "false" </description> </context-param> <!-- tiles support --> <context-param> <param-name>tiles-definitions</param-name> <param-value>/WEB-INF/tiles-defs.xml</param-value> </context-param> <!-- end of tiles --> <!-- WelcomeFile Filter --> <filter> <filter-name>WelcomeFile Filter</filter-name> <filter-class>org.apache.myfaces.webapp.filter.WelcomeFileFilter</filter-class> <description> Due to the manner in which the JSP / servlet lifecycle functions, it is not currently possible to specify default welcome files for a web application and map them to the MyFacesServlet. Normally they will be mapped to the default servlet for the JSP container. To offset this shortcoming, we utilize a servlet Filter which examines the URI of all incoming requests. </description> </filter> <!-- Extensions 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>10m</param-value> <description>Set the size limit for uploaded files. Format: 10 - 10 bytes 10k - 10 KB 10m - 10 MB 1g - 1 GB </description> </init-param> <init-param> <param-name>uploadThresholdSize</param-name> <param-value>300k</param-value> <description>Set the threshold size - files below this limit are stored in memory, files above this limit are stored on disk. Format: 10 - 10 bytes 10k - 10 KB 10m - 10 MB 1g - 1 GB </description> </init-param> <init-param> <param-name>uploadRepositoryPath</param-name> <param-value>/tmp</param-value> <description>Set the path where the intermediary files will be stored. </description> </init-param> </filter> <filter-mapping> <filter-name>extensionsFilter</filter-name> <url-pattern>*.jsf</url-pattern> </filter-mapping> <filter-mapping> <filter-name>extensionsFilter</filter-name> <url-pattern>/faces/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>securityFilter</filter-name> <url-pattern>*.jsf</url-pattern> </filter-mapping> <!-- Faces Servlet --> <servlet> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <!-- source code servlet (will not work with JSF virtual path mapping) --> <!-- this servlet is optional and for educational purposes only --> <!-- <servlet> <servlet-name>SourceCodeServlet</servlet-name> <servlet-class>org.apache.myfaces.util.servlet.SourceCodeServlet</servlet-class> </servlet> --> <!-- Faces Servlet Mapping --> <!-- virtual path mapping --> <!-- <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>/faces/*</url-pattern> </servlet-mapping> --> <!-- extension mapping --> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>*.jsf</url-pattern> </servlet-mapping> <!-- <servlet-mapping> <servlet-name>SourceCodeServlet</servlet-name> <url-pattern>*.source</url-pattern> </servlet-mapping> --> </web-app>
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN" "http://java.sun.com/dtd/web-facesconfig_1_1.dtd";> <faces-config> <!-- ========================= Locale Management ========================= --> <!-- Uncomment the following element and configure the default and supported locales for your application --> <application> <!-- <locale-config> <default-locale>en</default-locale> <supported-locale>en</supported-locale> </locale-config> --> <!-- tiles support --> <view-handler>org.apache.myfaces.application.jsp.JspTilesViewHandlerImpl</view-handler> <!-- end of tiles support --> </application> <!-- Uncomment the following element (after fixing the package name as needed) if your localized message bundle contains replacements for the standard converter or validator error message. --> <!-- <application> <message-bundle>org.apache.shale.blank.Bundle</message-bundle> </application> --> </faces-config>
