6 Replies Latest reply on Feb 7, 2011 5:26 PM by gonzalad

    Seam 3 and Websphere 6.1

    gonzalad Apprentice

      Hello,


      Does Seam 3 runs on Websphere 6.1 ?


      Do you plan to support Websphere 6.1 ?


      Thanks !


      P.S. I've just tried JSF 2 and WAS 6.1 on a little sample (no JSP !), it works fine.

        • 1. Re: Seam 3 and Websphere 6.1
          Jason Porter Master

          As long as they CDI support we'll support it.  I don't know where CDI support is on their roadmap.

          • 2. Re: Seam 3 and Websphere 6.1
            gonzalad Apprentice

            CDI support is targeted for Websphere 8 (Java EE 6 support).


            But in my company, we won't be having anytime soon Websphere 8 available.


            So, we need at least to add cdi / jsf2 / ... jars to Websphere 6.1 (J2EE 1.4 appserver) to use it with weld.


            I was more thinking about something like Tomcat level support for Websphere 6.1 (at the servlet level).


            WDYT ?

            • 3. Re: Seam 3 and Websphere 6.1
              Jason Porter Master

              I think you'll probably need at least a Servlet 2.5 container. You're welcome to create a JIRA and see we'll see how many votes in receives.

              • 4. Re: Seam 3 and Websphere 6.1
                Shane Bryzak Master

                I would recommend you try deploying an application with weld-servlet, which is part of the Weld download.  The documentation describes using it with Tomcat or Jetty, but I imagine it should be similar for Websphere:


                http://docs.jboss.org/weld/reference/1.1.0.Final/en-US/html/environments.html#d0e5221

                • 5. Re: Seam 3 and Websphere 6.1
                  gonzalad Apprentice

                  Thanks both of you !


                  I'll update this thread in a day or two - when I have more news (I'll try RF 4 and Seam 3).

                  • 6. Re: Seam 3 and Websphere 6.1
                    gonzalad Apprentice

                    For the moment, weld requires JVM 1.6 or more and cannot work on Websphere 6.1.


                    Websphere 6.1 uses IBM JVM 1.5.


                    When running weld-servlet, I have the following stackTrace :



                    [07/02/11 23:14:41:796 CET] 0000000f Version       I org.jboss.weld.bootstrap.WeldBootstrap <clinit> WELD-000900 1.1.0 (Final)
                    [07/02/11 23:14:41:921 CET] 0000000f ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC a ouvert le fichier de flux des incidents C:\Program Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv01\logs\ffdc\server1_0000000f_11.02.07_23.14.41_0.txt.
                    [07/02/11 23:14:41:968 CET] 0000000f ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC a fermé le fichier de flux des incidents C:\Program Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv01\logs\ffdc\server1_0000000f_11.02.07_23.14.41_0.txt.
                    [07/02/11 23:14:42:015 CET] 0000000f WebApp        E   Exception caught while initializing context 
                    java.lang.NoSuchMethodError: java/lang/String.isEmpty()Z
                         at org.jboss.weld.xml.BeansXmlHandler.getContainer(BeansXmlHandler.java:346)
                         at org.jboss.weld.xml.BeansXmlHandler.getContainer(BeansXmlHandler.java:339)
                         at org.jboss.weld.xml.BeansXmlHandler.startElement(BeansXmlHandler.java:293)
                         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
                         at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
                         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
                         at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
                         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
                         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
                         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
                         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
                         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
                         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
                         at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
                         at org.jboss.weld.xml.BeansXmlParser.parse(BeansXmlParser.java:100)
                         at org.jboss.weld.xml.BeansXmlParser.parse(BeansXmlParser.java:138)
                         at org.jboss.weld.bootstrap.WeldBootstrap.parse(WeldBootstrap.java:513)
                         at org.jboss.weld.environment.servlet.deployment.WebAppBeanDeploymentArchive.<init>(WebAppBeanDeploymentArchive.java:81)
                         at org.jboss.weld.environment.servlet.deployment.ServletDeployment.createWebAppBeanDeploymentArchive(ServletDeployment.java:34)
                         at org.jboss.weld.environment.servlet.deployment.ServletDeployment.<init>(ServletDeployment.java:25)
                         at org.jboss.weld.environment.servlet.Listener.createServletDeployment(Listener.java:115)
                         at org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:162)
                         at com.ibm.ws.wswebcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:653)