aspose file tools*
The moose likes Websphere and the fly likes Problem with Initialization of the JSF runtime on WebSphere 7 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Problem with Initialization of the JSF runtime on WebSphere 7 " Watch "Problem with Initialization of the JSF runtime on WebSphere 7 " New topic
Author

Problem with Initialization of the JSF runtime on WebSphere 7

Pedro Filho
Greenhorn

Joined: Sep 02, 2009
Posts: 6
Hi!

I have an app running perfectly in Websphere 6.1 but recently I've installed the Webphere 7 and when I'm starting the server I'm getting the error that I'll post bellow.

My web app has RichFaces, JSF 1.2, JBoss Seam and Trinidad.

What might be changed from WebSphere 6.1 to Websphere 7 ? Do I need to set anything??? What might be the cause of this error, I already google it and I found nothing.. I think there's something wrong with the required library portlet-bridge-impl-1.0.0-beta-2.jar that Trinidad uses..

Thank's in advance..



Initialization of the JSF runtime either failed or did not occurr. Review the server''s log for details.
java.lang.InstantiationException: org.apache.myfaces.portlet.faces.context.FacesContextFactoryImpl
at java.lang.J9VMInternals.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1325)
at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:537)
at javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:394)
at javax.faces.FactoryFinder.access$400(FactoryFinder.java:135)
at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:717)
at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:239)
at javax.faces.webapp.FacesServlet.init(FacesServlet.java:164)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:358)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:168)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1807)
at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:98)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:1008)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:929)
at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:608)
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:426)
at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:303)
at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:100)
at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:166)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:731)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:616)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:376)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:668)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1122)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1315)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:619)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:940)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:725)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2046)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:439)
at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:382)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$300(CompositionUnitMgrImpl.java:110)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:949)
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:349)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Problem with Initialization of the JSF runtime on WebSphere 7
 
Similar Threads
Xerces issue while deploying Web services on Websphere6.1
Problem with classloader with jaxb, spring, websphere
Installing axis2 (1.5.1) in Websphere 7
Problem with classloader with jaxb, spring, websphere
Migrating to Websphere app server 7 and RAD 7.5 from WSAD