WebSphere and JSF

[Oleg Tretyakov]

Hi All,

I have a some problem when try to start application on WebSphere. But it is giving the error...

[11.01.08 13:25:58:703 MSK] 0000002c jsp           E com.ibm.ws.jsp.taglib.TldParser logParseErrorMessage Failed to parse Tag Library [META-INF/c-1_0-rt.tld]: JSPG0235E: The JSP container failed to load the TagExtraInfo class [org.apache.taglibs.standard.tei.ImportTEI] 
[11.01.08 13:25:58:718 MSK] 0000002c jsp           W com.ibm.ws.jsp.taglib.TagLibraryCache loadTldsFromJar jsp error failed to load tld in jar. uri = [/WEB-INF/lib/standard.jar]
                                 com.ibm.ws.jsp.JspCoreException: org.xml.sax.SAXException: JSPG0235E: The JSP container failed to load the TagExtraInfo class [org.apache.taglibs.standard.tei.ImportTEI] 
at com.ibm.ws.jsp.taglib.TldParser.parseTLD(TldParser.java:266)
=============================================================================
[11.01.08 13:26:01:359 MSK] 0000002c jsp           E com.ibm.ws.jsp.taglib.TldParser logParseErrorMessage Failed to parse Tag Library [META-INF/html_basic.tld]: JSPG0235E: The JSP container failed to load the TagExtraInfo class [com.sun.faces.taglib.FacesTagExtraInfo] 
[11.01.08 13:26:01:359 MSK] 0000002c jsp           W com.ibm.ws.jsp.taglib.TagLibraryCache loadTldsFromJar jsp error failed to load tld in jar. uri = [/WEB-INF/lib/jsf-impl.jar]
                                 com.ibm.ws.jsp.JspCoreException: org.xml.sax.SAXException: JSPG0235E: The JSP container failed to load the TagExtraInfo class [com.sun.faces.taglib.FacesTagExtraInfo] 
at com.ibm.ws.jsp.taglib.TldParser.parseTLD(TldParser.java:266)

Can anybody help me to resolve this problem? The version of WAS is 6.1.0.

Thanks.

[Jaime Garc�a]

It is maybe a classloading issue. Please note that WebSphere comes with it's own version of JSF and JSTL jars and that maybe you want to use your own; to achieve this, you would deploy your application with those jars included, and set the classloader mode to PARENT_LAST.


Use the classloader viewer utility that comes with the administrative console to analize how the classloading is happening.

[Oleg Tretyakov]

Thank you for reply.

I want to use jsf libraries (jsf-impl.jar and standart.jar) from apps/web-inf/lib. But WebSphere is conflicting with it, because C:\WAS\IBM\WebSphere\AppServer\plugins\com.ibm.ws.webcontainer_2.0.0.jar contains jsf lib too.

following is the error I receive.

[15.01.08 17:59:39:109 MSK] 00000019 WebApp        E   Extension processor failed to initialize in factory: com.ibm.ws.jsp.webcontainerext.ws.WASJSPExtensionFactory@1e181e18
java.lang.NoSuchMethodError: com/sun/faces/util/Util.getLogger(Ljava/lang/String :wink: Ljava/util/logging/Logger;
at com.sun.faces.application.WebappLifecycleListener.<clinit>(WebappLifecycleListener.java:67)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:177)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:164)
...
 

Also the application is not work when I try to access to webapp

Error 403: SRVE0190E: File not found: /index.jsp

Please advise.

Thanks.

[Oleg Tretyakov]

Hi All,

I have configured class loader mode to PARENT_LAST and moved jsf-impl.jar, jsf-api.jar and javaee.jar into java/jre/lib/ext folder. So, WebSphere 6.1.0 uses JSF-1.2 instead of own JSF-1.1.

I try to run application and it does not work. The following error message is appeared in SystemOut.log:

[22.01.08 18:15:34:218 MSK] 00000019 WebApp        E   Extension
processor failed to initialize in factory: com.ibm.ws.jsf.extprocessor.JSFExtensionFactory@1cb61cb6
java.lang.IllegalStateException: Application was not properly initialized 
at startup, could not find Factory: javax.faces.render.RenderKitFactory
at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256)
at com.sun.faces.util.Util.verifyFactoriesAndInitDefaultRenderKit(Util.java:260)
at com.ibm.ws.jsf.configuration.FacesConfig.initialize(FacesConfig.java:96)
at com.ibm.ws.jsf.extprocessor.JSFExtensionFactory.createExtensionProcessor(JSFExtensionFactory.java:107)
at com.ibm.ws.webcontainer.webapp.WebApp.initializeExtensionProcessors(WebApp.java:1029)
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:255)
at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:271)
at com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:88)
at com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157)
at com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:653)
at com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:606)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:333)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:549)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1295)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1129)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:567)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:814)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:948)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2114)
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:340)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1498)

Please help me to resolve this issue.

Thanks.

[Marcelo Sousa Ancelmo]

Ok,

This thread is very old, but from times to times people come along with this issue, here is the breaktrough:
1 - You will need el-api.jar, jsf-api.jar, jsf-imp.jar and jstl.jar for Java Server Faces 1.1
2 - You will put the jars on WEB-INF/lib, as a shared library referenced by your Web Module or as references of optional-package declarations
3 - After deploying the application, change the value of the EAR ClassLoader to PARENT_LAST (Classes loaded with application class loader first option)
4 - Verify that this configuration is replicated to the WEB module classloader configuration, if not, change there also to "Classes loaded with application class loader first"
5 - Start / Restart de Web application
6 - Enjoy ;-)

This will work for the vast majority of JSF implementations (Myfaces, Icefaces) and frameworks tha rely on it (SEAM)

Regards,

[Ayan Dutta]

Hi Marcelo ,
I have one query regarding your post .
I am using WAS 6.1 with RAD .
You mentioned in point 3
"After deploying the application, change the value of the EAR ClassLoader to PARENT_LAST (Classes loaded with application class loader first option) "
I have followed this point by the following steps :
Navigating to Admin Cosole --> Applications -->Enterprise Applications -->Select Applicable EAR -->Manage Modules --> Select Applicable WAR --> Change Class loader order to "Classes loaded with application class loader first" .

Now , in point 4 you mentioned ..
"Verify that this configuration is replicated to the WEB module classloader configuration, if not, change there also to "Classes loaded with application class loader first" .
Can you explain this point a little bit more about the specific steps to verify the configuration replication ?
Regards,
Ayan Dutta

[Marcelo Sousa Ancelmo]

Hello Ayan,

The steps you described is to change the classloading policy for the web application. So you had done the step 4. It should work without any problem and is preferred if you have others web modules in your EAR that doesn't need the changed classloader policy.
I updated the steps, providing the paths in the administrative console.

1 - You will need el-api.jar, jsf-api.jar, jsf-imp.jar and jstl.jar for Java Server Faces 1.1
2 - You will put the jars on WEB-INF/lib, as a shared library referenced by your Web Module or as references of optional-package declarations
3 - After deploying the application, change the value of the EAR ClassLoader to PARENT_LAST (Classes loaded with application class loader first option) - Admin Cosole --> Applications -->Enterprise Applications -->Select EAR --> Class loading and update detection --> Change Class loader order to "Classes loaded with application class loader first"
4 - Verify that this configuration is replicated to the WEB module classloader configuration, if not, change there also to "Classes loaded with application class loader first" - Admin Cosole --> Applications -->Enterprise Applications -->Select EAR -->Manage Modules --> Select Applicable WAR --> Change Class loader order to "Classes loaded with application class loader first".
5 - Start / Restart de Web application

Regards,

[James T Thomas]

I know this is an older thread. I ran into the problems noted above and changing the class loading policy only made things worse for me so beware. Now the site doesw not come up at all. Error 404: SRVE0201E: Servlet [com.alstom.power.suppliernet.servlets.Login]: not a servlet class . We never had to change this before. I am going to seek out another solution and post it here if I do.

[Marcelo Sousa Ancelmo]

Hi James,

What is the version of JSF that you are trying to run? What is the version of WebSphere that you are using? Did you followed all the steps outlined here?

Regards,