a4j:commandButton causes NullPointerException in PartialViewContextImpl for IE7 requests if a <button> is present ----------------------------------------------------------------------------------------------------------------- Key: RF-12693 URL: https://issues.jboss.org/browse/RF-12693 Project: RichFaces Issue Type: Bug Security Level: Public(Everyone can see) Components: component-a4j-core Affects Versions: 4.3.0.M3 Environment: JBoss 7.1.1 with the stock "jsf-impl-2.1.7-jbossorg-2.jar" or upgraded to "jsf-impl-2.1.15.jar" Reporter: Justin Rosenberg Assignee: Brian Leathem Fix For: 4.3.0.CR1 Attachments: JSFButtonBug-1.0.0-SNAPSHOT.war, mojarraBug.zip Original Estimate: 15 minutes Remaining Estimate: 15 minutes When using the Richfaces a4j:commandButton I get the following stack trace when using Internet Explorer 7. This problem does not occur in IE8+ or Chrome. {code} 15:19:57,630 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception: java.lang.NullPointerException at com.sun.faces.context.PartialViewContextImpl.createPartialResponseWriter(PartialViewContextImpl.java:441) [jsf-impl-2.1.15.jar:2.1.15] at com.sun.faces.context.PartialViewContextImpl.access$300(PartialViewContextImpl.java:71) [jsf-impl-2.1.15.jar:2.1.15] at com.sun.faces.context.PartialViewContextImpl$DelayedInitPartialResponseWriter.getWrapped(PartialViewContextImpl.java:582) [jsf-impl-2.1.15.jar:2.1.15] at javax.faces.context.PartialResponseWriter.startDocument(PartialResponseWriter.java:115) [jsf-api-2.1.15.jar:2.1] at com.sun.faces.context.AjaxExceptionHandlerImpl.handlePartialResponseError(AjaxExceptionHandlerImpl.java:199) [jsf-impl-2.1.15.jar:2.1.15] at com.sun.faces.context.AjaxExceptionHandlerImpl.handle(AjaxExceptionHandlerImpl.java:124) [jsf-impl-2.1.15.jar:2.1.15] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119) [jsf-impl-2.1.15.jar:2.1.15] at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) [jsf-impl-2.1.15.jar:2.1.15] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.15.jar:2.1.15] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jsf-api-2.1.15.jar:2.1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:489) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_20] {code} I was surprised that this was only an IE7 issue, but I did find that PrimeFaces ran into a similar problem (http://code.google.com/p/primefaces/issues/detail?id=4361). Is there a workaround for this? Is this a Mojarra, RichFaces, or JBoss issue? I created http://java.net/jira/browse/JAVASERVERFACES-2666 in case this is a Mojarra problem, maybe we could help them resolve the issue.