5 Replies Latest reply on Dec 28, 2013 1:26 AM by ramsrib

    CXF 2.5 & JBoss question

    bapats
    bapats Mar 6, 2012 11:05 PM

      Is there any way to uninstall or not use the JBossWS-CXF that comes default with JBoss 7.1.0, and use the stock CXF instead?

      We want to use the STS capabilities in CXF 2.5.x which is not yet in JBossWS-CXF.

       

      If we try to deploy a CXF 2.5.0 war in the default JBoss 7.1.0, I see the following warnings. Are these due to the cxf 2.5.1 bundled in our war conflicting with JBossWS-CXF?

       

      15:55:49,717 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015893: Encountered invalid class name 'org.springframework.context.ApplicationContext,org.springframework.beans.BeansException' for service type 'org.apache.cxf.bus.factory'

      15:55:49,717 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015893: Encountered invalid class name 'org.springframework.context.ApplicationContext,org.springframework.beans.BeansException' for service type 'org.apache.cxf.bus.factory'

      15:55:50,014 WARN  [org.jboss.as.ee] (MSC service thread 1-6) JBAS011006: Not installing optional component org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation

                at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606)

                at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81)

                at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

                at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_31]

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_31]

                at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31]

       

       

      15:55:50,029 WARN  [org.jboss.as.ee] (MSC service thread 1-6) JBAS011006: Not installing optional component org.eclipse.jetty.continuation.Servlet3Continuation$1 due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.eclipse.jetty.continuation.Servlet3Continuation$1

                at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606)

                at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81)

                at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

                at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_31]

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_31]

                at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31]

       

       

      15:55:50,045 WARN  [org.jboss.as.ee] (MSC service thread 1-6) JBAS011006: Not installing optional component org.eclipse.jetty.continuation.Servlet3Continuation$2 due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.eclipse.jetty.continuation.Servlet3Continuation$2

                at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606)

                at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81)

                at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

                at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_31]

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_31]

                at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31]

       

       

       

       

      Thanks.

      • 18284 Views
      • Tags:
        • 1. Re: CXF 2.5 & JBoss question
          asoldano
          asoldano Mar 13, 2012 2:37 PM (in response to bapats)

          This *might* be possible through some classloading hack, but I've not tried.

          An alternative is to install the jbossws-native stack (which replaces jbossws-cxf).

            • Actions
          • 2. Re: CXF 2.5 & JBoss question
            ross.oreto
            ross.oreto Apr 17, 2012 1:17 PM (in response to asoldano)

            I also am experiencing this same issue trying to deploy a war to jboss 7. I tried to use jboss-deployment-structure to remove jboss cxf jars, this is what that file looks like:

             

            <jboss-deployment-structure>

            <deployment>

                <exclusions>

                    <module name="org.jboss.ws.cxf" />

                    <module name="org.apache.cxf" />

                    <module name="org.jboss.as.webservices" />

                    <module name="org.jboss.ws.jaxws-client" />

                </exclusions>

            </deployment>

            </jboss-deployment-structure>

             

            Is there another module I need to exclude?

              • Actions
            • 3. Re: CXF 2.5 & JBoss question
              steljboss
              steljboss Aug 17, 2012 8:24 AM (in response to bapats)

              Mayve a little bit late but if you are still interested check this answer here https://community.jboss.org/message/754242#754242

               

              although it is for JAX-RS it may give you a start to get this also done for JAX-WS

                • Actions
              • 4. Re: CXF 2.5 & JBoss question
                okidoky
                okidoky Aug 22, 2012 2:58 PM (in response to bapats)

                What I did is I created a modules/org/apache/cxf-2_6_2/main directory, downloaded a copy of Apache CXF 2.6.2, and copied its modules/*.jar to that main directory.

                I then listed all the jar files in module.xml, and named the module org.apache.cxf-2_6_2

                In my war project, the META-INF/MANIFEST.MF has:

                Dependencies: org.apache.cxf-2_6_2

                 

                It of course gives me a pile of other errors, but that's quite common with CXF WS-security/trust.

                  • Actions
                • 5. Re: CXF 2.5 & JBoss question
                  ramsrib
                  ramsrib Dec 28, 2013 1:26 AM (in response to okidoky)

                  These exceptions are not because of CXF conflicting with JBoss's webservices subsystem.

                  It seems to be a bug in JBoss. Even if you disable the JBoss's webservices subsystem, you can see these exceptions in your server log.

                   

                  And these exceptions will not affect any anything & can be ignored.

                   

                  Refer :

                  JBAS011054: Could not find default constructor for class org.springframework.web.context.request.async.StandardServletAsyncWebRequest

                    • Actions