Topic: JSF 1.2
Application Server: JBoss 4.2.2GA
Exception:
Exception sending context initialized event to listener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
javax.faces.FacesException: Can't parse configuration file: jndi:/localhost/JSFWebapp/WEB-INF/faces-config.xml: Error at line 17 column 5: The element type "managed-bean-scope" must be terminated by the matching end-tag "</managed-bean-scope>".
at com.sun.faces.config.ConfigureListener.parse(ConfigureListener.java:1438)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:376)
at org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitialized(JBossJSFConfigureListener.java:69)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3856)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4361)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:790)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:770)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
Resolution:
The exception occurs due to an error in the JSF-specific configuration file, faces-config.xml, which must comply with XML rules for well-formed-ness and validity. Check for an incorrectly terminated XML element or an incorrectly spelled element, or other such errors in the faces-config.xml
The error message in the Server console log also pin-points the line number where the error has occured, fairly well.
No comments:
Post a Comment