Re: Unable to parse document 'jndi:/server/jsfexample/WEB-INF/pretty-config.xml':

Splash Forums PrettyFaces Users Unable to parse document 'jndi:/server/jsfexample/WEB-INF/pretty-config.xml': Re: Unable to parse document 'jndi:/server/jsfexample/WEB-INF/pretty-config.xml':


Yes, please make sure we are seeing the most recent stacktrace.

For me the most interesting part of the stacktrace is:

Caused by: com.sun.faces.config.ConfigurationException: Unable to parse document 'jndi:/server/jsfexample/WEB-INF/pretty-config.xml': null

at com.sun.faces.config.ConfigManager$

at com.sun.faces.config.ConfigManager$

at java.util.concurrent.FutureTask$Sync.innerRun(


at com.sun.faces.config.ConfigManager.getConfigDocuments(

... 43 more

Caused by: java.lang.IllegalStateException

at com.sun.faces.config.ConfigManager$ParseTask.getTransformer(

at com.sun.faces.config.ConfigManager$ParseTask.getDocument(

at com.sun.faces.config.ConfigManager$

I just looked into the Mojarra source. They are using some kind of provider pattern to build a list of XML files to parse. Then they starting parsing them in separate threads (ParseTask). The ParseTask.getTransformer() method tries to detect the content of the XML file by looking at the namespaces of the root element. They seem to use some kind of XSLT transformations for files like old Facelets stuff there.

Thats what I got so far. I really think it is a Mojarra or Glassfish integration issue.