6 Replies Latest reply on Jan 30, 2008 9:37 AM by Jay Balunas

    Seam with WAS 6.1 EJB3 feature pack

    Lanh Tran Newbie

      Hi,
      I am uing Websphere 6.1.0.13 EJB3 feature patch. I tried to adopt the Jee5 hotel booking example (packaged with Seam 2.0 CR3) but it doesn't work. Have anyone tried that before?
      Does Jboss have a EJB3 "plugin" for WAS?

      Thanks

        • 1. Re: Seam with WAS 6.1 EJB3 feature pack
          Pete Muir Master

          I've not heard of that working, but if you post the problems you see there may be some who can help you. If you get it working and can post a tutorial/blog article that would be great!

          • 2. Re: Seam with WAS 6.1 EJB3 feature pack
            Lisa Mark Newbie

            Hi,
            I also tried SEAM+EJB 3.0 with/without feature pack on WAS 6.1 but no success yet.

            My next try is on :

            http://www-306.ibm.com/software/webservers/appserv/community/

            They say its a Java EE5 server.

            I'll post my coments after testing a SEAM EJB 3.0 example on that server.

            If anyone already did some work on this, then please share your comments.

            Thanks

            • 3. Re: Seam with WAS 6.1 EJB3 feature pack
              Lanh Tran Newbie

              By adding all the dependent jar filenames to the Class-Path inside the MANIFEST file of the example jar file (jboss-seam-jee5.jar), I can successfully deploy the JEE5 booking example on WAS.
              But when I try to run the example, there is an error as following:

              On the browser screen:
              Error 500: org/jboss/seam/ui/component/UISeamCommandBase.getValueExpression(Ljava/lang/String;)Ljavax/el/ValueExpression;

              And in the SystemOut.log:

              [5/11/07 09:28:26:289 EST] 00000020 compiler I Added Library from: wsjar:file:/C:/IBM/WebSphere/AppServer/profiles/LTRAN/installedApps/wsd25Node02Cell/Booking_EE5.ear/seam_jee5.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/richfaces.taglib.xml
              [5/11/07 09:28:26:648 EST] 00000020 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: Faces Servlet. Exception thrown : java.lang.NoSuchMethodError: org/jboss/seam/ui/component/UISeamCommandBase.getValueExpression(Ljava/lang/String;)Ljavax/el/ValueExpression;
              at org.jboss.seam.ui.component.UISeamCommandBase.getUrl(UISeamCommandBase.java:86)
              at org.jboss.seam.ui.renderkit.LinkRendererBase.doEncodeBegin(LinkRendererBase.java:26)
              at org.jboss.seam.ui.util.cdk.RendererBase.encodeBegin(RendererBase.java:79)
              at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:717)
              at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:242)
              at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249)
              at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249)
              at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:594)
              at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
              at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:216)
              at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
              at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:220)
              at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:118)
              at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
              at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:995)
              at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:930)
              at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
              at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
              at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85)
              at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
              at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44)
              at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
              at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
              at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
              at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
              at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
              at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:150)
              at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
              at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
              at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
              at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:768)
              at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:676)
              at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498)
              at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:486)
              at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3276)
              at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
              at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)
              at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455)
              at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:113)
              at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
              at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
              at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
              at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
              at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
              at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
              at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
              at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
              at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
              at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
              at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)

              Any suggestion?

              Thanks

              • 4. Re: Seam with WAS 6.1 EJB3 feature pack
                Pete Muir Master

                I would guess that you have JSF 1.1 rather than 1.2 running somewhere on your classpath.

                • 5. Re: Seam with WAS 6.1 EJB3 feature pack
                  Lanh Tran Newbie

                  Where to find out which version of JSF is running?

                  There is one warning when I started the application:
                  [7/11/07 15:45:49:511 EST] 00000022 jsf W com.ibm.ws.jsf.configuration.FacesConfigParser parseShared FacesConfigParser.parseShared(): unable to locate : [el-resolver]

                  I don't know if this has anything to do with the above reported error?

                  Thanks

                  • 6. Re: Seam with WAS 6.1 EJB3 feature pack
                    Jay Balunas Master

                    The websphere chapter has been checked into svn.

                    It has examples for:

                    JEE5 with EJB3
                    JPA with seam pojo components and JPA transactions
                    seam-gen EAR deployment and modification.

                    Hopefully this will cover all of your needs. Please let me know if you spot a problem or have questions.