Topic
6 replies Latest Post - ‏2010-09-29T17:51:42Z by SystemAdmin
acartjam
acartjam
2 Posts
ACCEPTED ANSWER

Pinned topic MyFaces 1.1.5 and Websphere 7.0

‏2010-05-20T02:07:45Z |
My team is in the process of migrating our applications from WAS 6.0 to WAS 7.0. Our applications use MyFaces 1.1.5 and Tomahawk 1.1.6. Since WAS 7.0 comes with MyFaces 1.2, we have the version of MyFaces (1.1.5) in the WebINF/lib folder and set the classpath to parent last so that the server loads and uses our version of the MyFaces jars...

myfaces-api-1.1.5.jar - version=1.1.5
myfaces-impl-1.1.5.jar - version 1.1.5
When we tried running the application on the WAS 7.0 server we get the following error...

Message: org/apache/myfaces/taglib/core/ViewTag.setJspId(Ljava/lang/String;)V

Details: java.lang.NoSuchMethodError: org/apache/myfaces/taglib/core/ViewTag.setJspId(Ljava/lang/String;)V
Causes
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Stack Trace
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

com.ibm._jsp._baseLayout._jspx_meth_f_view_0(_baseLayout.java:1615)
com.ibm._jsp._baseLayout._jspService(_baseLayout.java:168)
com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1655)
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1595)
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:104)
com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:895)
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:932)
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:500)
com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:121)
com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:239)
com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionProcessor.handleRequest(AbstractJSPExtensionProcessor.java:340)
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDispatcher.java:673)
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:1045)
org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:527)
org.apache.struts.tiles.TilesUtilImpl.doInclude(TilesUtilImpl.java:137)
org.apache.struts.tiles.TilesUtil.doInclude(TilesUtil.java:177)
org.apache.struts.taglib.tiles.InsertTag.doInclude(InsertTag.java:756)
org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsertTag.java:881)
org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:473)
com.ibm._jsp._today._jspx_meth_tiles_insert_0(_today.java:213)
com.ibm._jsp._today._jspService(_today.java:91)
com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1655)
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1595)
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:104)
com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:895)
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:932)
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:500)
com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:121)
com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:239)
com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionProcessor.handleRequest(AbstractJSPExtensionProcessor.java:340)
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:341)
org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:419)
org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:211)
org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:132)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:140)
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1655)
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1595)
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:131)
org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:147)
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
com.highmark.itgtrk.framework.web.WebAppFilter.doFilter(WebAppFilter.java:216)
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:895)
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:932)
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:500)
com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3810)
com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)
com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)
com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:183)
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:455)
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:384)
com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)
Can anyone help us determine why the server is not getting our version of MyFaces in WAS 7.0? Thanks for your help in advance.
Updated on 2010-09-29T17:51:42Z at 2010-09-29T17:51:42Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    37422 Posts
    ACCEPTED ANSWER

    Re: MyFaces 1.1.5 and Websphere 7.0

    ‏2010-05-20T06:28:55Z  in response to acartjam
    Hi Acartjam;

    Did you try setting "Class Loader" setting of your application to "parent last"?

    Regards,
    Orkan
    • acartjam
      acartjam
      2 Posts
      ACCEPTED ANSWER

      Re: MyFaces 1.1.5 and Websphere 7.0

      ‏2010-05-20T13:00:57Z  in response to SystemAdmin
      Thanks for your quick response and yes, the class loader for our application is set to parent last.

      Our application works on our local WAS 7.0 server within RAD 7.5; however, we are having this problem after we deployed that application to run on the web with WAS 7.0. We compared to make sure the server is configured the same way that we have it configured within RAD and everything seems to be the same. We've been working on this issue for weeks and we still haven't got any further along in resolving this issue.
  • SystemAdmin
    SystemAdmin
    37422 Posts
    ACCEPTED ANSWER

    Re: MyFaces 1.1.5 and Websphere 7.0

    ‏2010-07-20T15:45:00Z  in response to acartjam
    Hi ,
    I believe this a bug in Tomcat , I dont know how much it has to do with specific to websphere as no other apps really have this issue .

    refer to http://www.mail-archive.com/users@myfaces.apache.org/msg49544.html

    Thanks,
    vinodh
    • SystemAdmin
      SystemAdmin
      37422 Posts
      ACCEPTED ANSWER

      Re: MyFaces 1.1.5 and Websphere 7.0

      ‏2010-07-20T19:20:05Z  in response to SystemAdmin
      Hi,
      Im using WAS 7.0 and ILOG 7.1 and facing the same issue , I saw this related to some myfaces library , but i tried updating the lib to myfaces 2.x and tomahawk-1.9 , I got some other error .Basically i couldnt able to log into RES at all.
      Any fix or updated please let me know
      Thanks,
      Vinodh
      • SystemAdmin
        SystemAdmin
        37422 Posts
        ACCEPTED ANSWER

        Re: MyFaces 1.1.5 and Websphere 7.0

        ‏2010-07-21T12:28:22Z  in response to SystemAdmin
        I checked one other system we have where we installed ILOG 7.0.1 on WAS in unix box , im able to access RES Console . I tried to find is something different in classloader or anything , but no clue .
        Did any one find a solutions or workaround ? please update.
        Thanks,
        Vinodh
        • SystemAdmin
          SystemAdmin
          37422 Posts
          ACCEPTED ANSWER

          Re: MyFaces 1.1.5 and Websphere 7.0

          ‏2010-09-29T17:51:42Z  in response to SystemAdmin
          Hello,

          The problem is most likely that the cache for you JSP pages was not refreshed since you changed the classloader policy. You need to clear this cache to restore the application

          In the document WebSphereILOGJRules\doc\j2ee\install-readme.html you will find information about this problem and other issues related to installation.

          I reproduce the information for the record here :
          1. Stop Rule Team Server in the WebSphere administration console.

          2. Change the class loading sequence as explained in the installation documentation *WebSphere ILOG
          JRules V7.1: Installing on WebSphere Application Server > Installing Rule Execution Server > Installing Rule Execution Server on WebSphere Application Server V7.1 > Deploying the Rule Execution Server Management EAR* (parent last instead of parent first).

          3. Remove JSP compiled files in your WebSphere Application Server profile (delete the directory <WASProfile>/temp/<nodeName>/<serverName>/teamserver-WAS7).

          4. Start Rule Team Server in the WebSphere administration console.

          Note: For a managed server (a server with a deployment manager), ensure that the teamserver.war file is removed also from the temporary folder of the deployment manager profile (for example, {WAS_INSTALL_ROOT}/profiles/default/temp/wscache/ILOG/Rule Team Server/), where {WAS_INSTALL_ROOT} is the install home for the Deployment manager (for example, /WebSphere/V7ILGDM/DeploymentManager).
          I hope this will be helpful.

          My 2 cents,
          Alain