Last week, I learned how to avoid the error in GlassFishConfigureListener occuring when deploying a JSF + Richfacess-driven application in WebSphere. Here is the example stack trace:
E com.ibm.ws.webcontainer.webapp.WebApp notifyServletContextCreated SRVE0283E: Exception caught while initializing context: {0} java.lang.NoSuchMethodError: com/sun/faces/config/GlassFishConfigureListener.scanWebXml(Z)V at com.sun.faces.config.GlassFishConfigureListener.contextInitialized(GlassFishConfigureListener.java:46) at com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:1667) at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:368) at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:294) at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:100) at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:166)
I found out that there's a bug in Richfaces or higher with JSF 1.2_07 or lower when deploying to WAS 7. I reverted my Richfaces to 3.3.1.GA instead of 3.3.3.Final, upgraded my web app's JSF reference implementation to JSF-1.2_12 and it worked.
No comments:
Post a Comment