You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Martin Marinschek (JIRA)" <de...@myfaces.apache.org> on 2007/09/28 18:08:50 UTC

[jira] Resolved: (MYFACES-1287) Provider for javax.xml.parsers.SAXParserFactory cannot be found

     [ https://issues.apache.org/jira/browse/MYFACES-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Marinschek resolved MYFACES-1287.
----------------------------------------

       Resolution: Cannot Reproduce
    Fix Version/s: 1.1.6

I cannot reproduce this problem on a current websphere version with the latest MyFaces head. Seems to be a singular problem with your library configuration.

regards,

Martin

> Provider for javax.xml.parsers.SAXParserFactory cannot be found
> ---------------------------------------------------------------
>
>                 Key: MYFACES-1287
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1287
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 1.1.3
>         Environment: WebSphere Platform 6.0 [BASE 6.0.2.3 cf30542.05]  
> Host Operating System is Windows XP, version 5.1
> Java version = J2RE 1.4.2 IBM Windows 32 build cn142-20050609 (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
> --- MyFaces lib update to 2006/04/18 ---
> myfaces-api-1.1.3-SNAPSHOT.jar                 
> myfaces-impl-1.1.3-SNAPSHOT.jar                
> myfaces-shared-tomahawk-2.0.1-SNAPSHOT.jar     
> tomahawk-1.1.2-SNAPSHOT.jar               
> Classpath = D:\IBM\Rational\SDP\6.0\runtimes\base_v6/profiles/default/properties;D:\IBM\Rational\SDP\6.0\runtimes\base_v6/properties;D:\IBM\Rational\SDP\6.0\runtimes\base_v6/lib/bootstrap.jar;D:\IBM\Rational\SDP\6.0\runtimes\base_v6/lib/j2ee.jar;D:\IBM\Rational\SDP\6.0\runtimes\base_v6/lib/lmproxy.jar;D:\IBM\Rational\SDP\6.0\runtimes\base_v6/lib/urlprotocols.jar
> Java Library path = D:\IBM\Rational\SDP\6.0\runtimes\base_v6\java\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\IBM\Rational\SDP\6.0\runtimes\base_v6\bin;D:\IBM\Rational\SDP\6.0\runtimes\base_v6\java\bin;D:\IBM\Rational\SDP\6.0\runtimes\base_v6\java\jre\bin;D:\IBM\Rational\SDP\6.0\eclipse\jre\bin;C:\orant\bin;E:\maven-2.0.2\bin;E:\oracle\product\10.2.0\client_2\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Intel\DMIX;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\Subversion\bin;C:\PROGRA~1\ATT\Graphviz\bin;C:\Program Files\Sun\jstudio_ent8\AppServ8.1UR2\bin;C:\Program Files\Sun\jstudio_ent8\ide\uml1\modules\DoorsIntegrationFiles\modules\bin
>            Reporter: Michael Cheng
>            Priority: Critical
>             Fix For: 1.1.6
>
>
> While deploy the new snapshot of the Myfaces lib, the startup console shows the following error message.
> [4/17/06 18:08:57:266 CST] 0000000a FacesConfigur I org.apache.myfaces.config.FacesConfigurator feedStandardConfig Reading standard config org/apache/myfaces/resource/standard-faces-config.xml
> [4/17/06 18:08:57:625 CST] 0000000a WebApp        E   Provider for javax.xml.parsers.SAXParserFactory cannot be found
> [4/17/06 18:08:57:672 CST] 0000000a ServletWrappe E   SRVE0100E: Did not realize  init() exception thrown by servlet Faces Servlet: java.lang.IllegalStateException: No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions!
> If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml.
> A typical config looks like this;
> <listener>
>   <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
> </listener>
> 	at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:90)
> 	at javax.faces.webapp.FacesServlet.init(FacesServlet.java:88)
> 	at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:274)
> 	at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1398)
> 	at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:86)
> 	at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:759)
> 	at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:502)
> 	at com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:391)
> 	at com.ibm.ws.webcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:114)
> 	at com.ibm.ws.webcontainer.VirtualHost.addWebApplication(VirtualHost.java:127)
> 	at com.ibm.ws.webcontainer.WebContainer.addWebApp(WebContainer.java:854)
> 	at com.ibm.ws.webcontainer.WebContainer.addWebApplication(WebContainer.java:807)
> 	at com.ibm.ws.runtime.component.WebContainerImpl.install(WebContainerImpl.java:167)
> 	at com.ibm.ws.runtime.component.WebContainerImpl.start(WebContainerImpl.java:391)
> 	at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1228)
> 	at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1067)
> 	at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:547)
> 	at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:751)
> 	at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:892)
> 	at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2003)
> 	at com.ibm.ws.runtime.component.ComponentImpl.runAsynchronousInitializer(ComponentImpl.java:159)
> 	at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplications(ApplicationMgrImpl.java:745)
> 	at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:524)
> 	at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820)
> 	at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649)
> 	at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:149)
> 	at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820)
> 	at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649)
> 	at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:402)
> 	at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:187)
> 	at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133)
> 	at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387)
> 	at com.ibm.ws.runtime.WsServer.main(WsServer.java:53)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
> 	at java.lang.reflect.Method.invoke(Method.java:391)
> 	at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:218)
> 	at java.lang.Thread.run(Thread.java:568)
> The file list is shown as follows:-
> commons-beanutils-1.7.0.jar                    
> commons-codec-1.3.jar                          
> commons-collections-3.1.jar                    
> commons-digester-1.6.jar                       
> commons-el-1.0.jar                             
> commons-fileupload-1.0.jar                     
> commons-lang-2.1.jar                           
> commons-logging-1.0.4.jar                      
> commons-validator-1.2.0.jar                    
> jstl-1.1.0.jar                                 
> myfaces-api-1.1.3-SNAPSHOT.jar                 
> myfaces-impl-1.1.3-SNAPSHOT.jar                
> myfaces-shared-tomahawk-2.0.1-SNAPSHOT.jar     
> oro-2.0.8.jar                                  
> tomahawk-1.1.2-SNAPSHOT.jar                    
> xml-apis-1.0.b2.jar                            

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.