Setup: JSF, PrimeFaces 3.2, Omnifaces 1.1, JBoss AS 7.1.1, Final, Mojarra 2.1.7
I have a simple page (listed below) and I have set up omnifaces to deal with ViewExpiredExceptions for ajax calls. When the listed below page expires and I click on a primefaces button (ajax) on IE8, the expired error page shows up but with the following javascript error:
Message: Object doesn't support this property or method, Line: 1 Char: 5500 Code: 0 URI: blah blah/mywebapp/javax.faces.resource/primefaces.js.xhtml?ln=primefaces&v=3.2
It doesn't seem to produce an error on other browsers.
My page (home.xhtml):
<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
template="/WEB-INF/templates/layout.xhtml">
<ui:define name="body">
<h:form id="form_search">
<p:commandButton id="idbtn1"
actionListener="#{bean.doSomething}"
value="Do something (ajax)!">
</p:commandButton>
<p:commandButton id="idbtn2" ajax="false"
actionListener="#{bean.doSomething}"
value="Do something!">
</p:commandButton>
</h:form>
</ui:define>
</ui:composition>
The timeout error page: expired.xhtml
<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
template="/WEB-INF/templates/layout.xhtml">
<ui:define name="body">
Your session has timed out.
</ui:define>
</ui:composition>
The template layout.xhtml
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:ui="http://java.sun.com/jsf/facelets">
<f:view contentType="text/html">
<h:head>
<f:facet name="first">
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta http-equiv="Cache-Control" content="no-cache, no-store, must- revalidate" />
<meta http-equiv="Pragma" content="no-cache" />
<meta http-equiv="Expires" content="0" />
</f:facet>
<base href="${facesContext.externalContext.requestContextPath}" />
</h:head>
<h:body>
<ui:insert name="body"></ui:insert>
</h:body>
</f:view>
</html>
Web.xml has among other bits:
<error-page>
<exception-type>javax.faces.application.ViewExpiredException</exception-type>
<location>/WEB-INF/errorpages/expired.xhtml</location>
</error-page>
<filter>
<filter-name>facesExceptionFilter</filter-name>
<filter-class>org.omnifaces.filter.FacesExceptionFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>facesExceptionFilter</filter-name>
<servlet-name>Faces Servlet</servlet-name>
</filter-mapping>
When I click on the second button after expiration, then the expired page shows without javascript errors.
Any ideas?
This is a known issue of PrimeFaces
update="@all"
in IE based browsers. The entire view is been replaced bydocument.write()
, however IE based browsers doesn't properly load/initialize any<script>
resources. See also this PrimeFaces forum topic. This will be addressed for PrimeFaces version 3.4.2.Until then, you can workaround it using the following JavaScript
which needs to be loaded after PrimeFaces own JS resources; this can be done by referencing it in
<h:body>
withtarget="head"
.Note that this assumes that the current view is using PrimeFaces components which should in turn force auto-inclusion of
primefaces.js
andjquery.js
scripts. Otherwise you've to manually declare them.