0 Replies Latest reply on Nov 17, 2017 5:12 PM by Jason Glass

    Another "Using XMLBeans binding for JAX-WS web services" Problem

    Jason Glass Newbie

      Hi All!  I've been struggling with this for two days now and I'm closer - but still getting an exception and I was hoping someone could possibly help be troubleshoot or overcome it!  This old discussion is my EXACT problem:

      Using XMLBeans binding for JAX-WS web services

       

      prabahard also had the same problem here https://developer.jboss.org/thread/270213

       

      I'm using JBoss EAP 7.0.0

       

      Now I know XMLBeans is old and out the door - but using JAX-B to generate my source is not working properly as some of the source classes have the type xsd:anyType.  When I try and unmarshal the XML from a web service call - the anyType values are gone so I'm trying to use XMLBeans to see if they're handled better!


      I've created the following two modules as per the above thread:

      Path: C:\jboss-eap-7.0\modules\org\apache\cxf\xmlbeans\main\module.xml


      Containing:

      <module xmlns="urn:jboss:module:1.1" name="org.apache.cxf.xmlbeans">
        <resources>
          <resource-root path="cxf-rt-databinding-xmlbeans-3.1.6.jar"/>
        </resources>
        <dependencies>
          <module name="org.apache.xmlbeans" slot="main" export="true"/> 
        </dependencies>
      </module>
      

      With cxf-rt-databinding-xmlbeans-3.1.6.jar located in the same folder

       

      Note: I also tried cxf-rt-databinding-xmlbeans-3.1.4.jar since JBoss EAP 7.0.0 is using this version but got same results.

       

      Path: C:\jboss-eap-7.0\modules\org\apache\xmlbeans\main\module.xml

       

      Containing:

      <module xmlns="urn:jboss:module:1.1" name="org.apache.xmlbeans">
        <resources>
          <resource-root path="jsr173_1.0_api.jar"/>
          <resource-root path="resolver.jar"/>
          <resource-root path="xbean.jar"/>
          <resource-root path="xbean_xpath.jar"/>
      <resource-root path="xmlbeans-2.6.0.jar"/>
      <resource-root path="xmlbeans-qname.jar"/>
      <resource-root path="xmlpublic.jar"/>
      <!--resource-root path="xmlschema-core-2.2.2.jar"/-->
        </resources>
        <dependencies>
          <module name="javax.api" slot="main" export="true"/> 
        </dependencies>
      </module>
      

       

      Note: the commented out xmlschema-core-2.2.2.jar

       

      In my Manifest I have:

      Manifest-Version: 1.0
      Dependencies: org.jboss.ws.cxf.jbossws-cxf-client services export, org.apache.xmlbeans services export
      

       

      My web service is annotated with:

      @org.apache.cxf.annotations.DataBinding(org.apache.cxf.xmlbeans.XmlBeansDataBinding.class)
      

       

      I also have this in the CXF.xml file:

      <jaxws:endpoint
          id="JVTOrderManagementSessionService"
          implementor="net.mycompany.utility.xxx.JVTOrderManagementSessionWS"
          address="http://localhost:8080/XXXMLBeansProxyEJB/JVTOrderManagementSessionService/JVTOrderManagementSessionWS">
          <jaxws:dataBinding>
             <bean class="org.apache.cxf.xmlbeans.XmlBeansDataBinding" />
          </jaxws:dataBinding>
      </jaxws:endpoint>
      

       

      With all of the above, JBoss appears to have begun trying to use XMLBeans as the databinding instead of JAX-B (yay!)

       

      But now I get this exception:

      14:34:13,682 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0207: Starting subdeployment (runtime-name: "XXXXMLBeanProxyEJB.jar")
      14:34:13,684 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0001: /C:/jboss-eap-7.0/standalone/deployments/XXXXMLBeanProxyEAR.ear/XXXXMLBeanProxyEJB.jar/META-INF/jboss-deployment-structure.xml in subdeployment ignored. jboss-deployment-structure.xml is only parsed for top level deployments.
      14:34:14,953 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment XXXXMLBeanProxyEAR.ear
      14:34:15,016 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-5) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
      14:34:15,279 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment XXXXMLBeanProxyEJB.jar
      14:34:15,292 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'JVTOrderManagementSessionWS' in deployment unit 'subdeployment "XXXXMLBeanProxyEJB.jar" of deployment "XXXXMLBeanProxyEAR.ear"' are as follows:
      
      
      14:34:15,318 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0006: Starting Services for CDI deployment: XXXXMLBeanProxyEAR.ear
      14:34:15,378 INFO  [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 2.3.3 (redhat)
      14:34:15,422 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0009: Starting weld service for deployment XXXXMLBeanProxyEAR.ear
      14:34:15,743 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
      14:34:15,744 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
      14:34:15,745 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
      14:34:15,746 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
      14:34:15,784 INFO  [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=JVTOrderManagementSessionWS
      address=http://localhost:8080/XXXXMLBeanProxyEJB/JVTOrderManagementSessionService/JVTOrderManagementSessionWS
      implementor=net.mycompany.utility.XXX.JVTOrderManagementSessionWS
      serviceName={http://XXX.utility.mycompany.net/}JVTOrderManagementSessionService
      portName={http://XXX.utility.mycompany.net/}JVTOrderManagementSessionWSPort
      annotationWsdlLocation=null
      wsdlLocationOverride=null
      mtomEnabled=false
      14:34:16,214 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 59) WFLYCLINF0002: Started client-mappings cache from ejb container
      14:34:16,753 INFO  [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://XXX.utility.mycompany.net/}JVTOrderManagementSessionService from class net.mycompany.utility.XXX.JVTOrderManagementSessionWS
      14:34:16,844 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.subunit."XXXXMLBeanProxyEAR.ear"."XXXXMLBeanProxyEJB.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."XXXXMLBeanProxyEAR.ear"."XXXXMLBeanProxyEJB.jar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment "XXXXMLBeanProxyEJB.jar" of deployment "XXXXMLBeanProxyEAR.ear"
       at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
       at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
       at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
       at java.lang.Thread.run(Thread.java:745)
      Caused by: java.lang.NoClassDefFoundError: org/apache/ws/commons/schema/XmlSchemaException
       at org.apache.cxf.xmlbeans.XmlBeansDataBinding.initialize(XmlBeansDataBinding.java:114)
       at org.apache.cxf.service.factory.AbstractServiceFactoryBean.initializeDataBindings(AbstractServiceFactoryBean.java:86)
       at org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:467)
       at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFromClass(JaxWsServiceFactoryBean.java:696)
       at org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:527)
       at org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:261)
       at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:199)
       at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:102)
       at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:168)
       at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:211)
       at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:460)
       at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:338)
       at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:79)
       at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:255)
       at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:543)
       at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:234)
       at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:97)
       at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:59)
       at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73)
       at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
       ... 5 more
      Caused by: java.lang.ClassNotFoundException: org.apache.ws.commons.schema.XmlSchemaException from [Module "deployment.XXXXMLBeanProxyEAR.ear:main" from Service Module Loader]
       at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198)
       at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363)
       at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351)
       at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93)
       ... 25 more
      
      14:34:16,875 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 59) WFLYCLINF0003: Stopped client-mappings cache from ejb container
      14:34:16,885 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "XXXXMLBeanProxyEAR.ear")]) - failure description: {
          "WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"XXXXMLBeanProxyEAR.ear\".\"XXXXMLBeanProxyEJB.jar\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"XXXXMLBeanProxyEAR.ear\".\"XXXXMLBeanProxyEJB.jar\".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment \"XXXXMLBeanProxyEJB.jar\" of deployment \"XXXXMLBeanProxyEAR.ear\"
          Caused by: java.lang.NoClassDefFoundError: org/apache/ws/commons/schema/XmlSchemaException
          Caused by: java.lang.ClassNotFoundException: org.apache.ws.commons.schema.XmlSchemaException from [Module \"deployment.XXXXMLBeanProxyEAR.ear:main\" from Service Module Loader]"},
          "WFLYCTL0180: Services with missing/unavailable dependencies" => [
              "jboss.deployment.unit.\"XXXXMLBeanProxyEAR.ear\".WeldStartService is missing [jboss.deployment.subunit.\"XXXXMLBeanProxyEAR.ear\".\"XXXXMLBeanProxyEJB.jar\".jndiDependencyService]",
              "jboss.deployment.subunit.\"XXXXMLBeanProxyEAR.ear\".\"XXXXMLBeanProxyEJB.jar\".batch.environment is missing [jboss.deployment.subunit.\"XXXXMLBeanProxyEAR.ear\".\"XXXXMLBeanProxyEJB.jar\".beanmanager]",
              "jboss.naming.context.java.comp.XXXXMLBeanProxyEAR.XXXXMLBeanProxyEJB.JVTOrderManagementSessionWS.InAppClientContainer is missing [jboss.naming.context.java.comp.XXXXMLBeanProxyEAR.XXXXMLBeanProxyEJB.JVTOrderManagementSessionWS]",
              "jboss.naming.context.java.comp.XXXXMLBeanProxyEAR.XXXXMLBeanProxyEJB.JVTOrderManagementSessionWS.ValidatorFactory is missing [jboss.naming.context.java.comp.XXXXMLBeanProxyEAR.XXXXMLBeanProxyEJB.JVTOrderManagementSessionWS]",
              "jboss.deployment.unit.\"XXXXMLBeanProxyEAR.ear\".deploymentCompleteService is missing [jboss.deployment.subunit.\"XXXXMLBeanProxyEAR.ear\".\"XXXXMLBeanProxyEJB.jar\".deploymentCompleteService]",
              "jboss.naming.context.java.comp.XXXXMLBeanProxyEAR.XXXXMLBeanProxyEJB.JVTOrderManagementSessionWS.Validator is missing [jboss.naming.context.java.comp.XXXXMLBeanProxyEAR.XXXXMLBeanProxyEJB.JVTOrderManagementSessionWS]",
              "jboss.deployment.subunit.\"XXXXMLBeanProxyEAR.ear\".\"XXXXMLBeanProxyEJB.jar\".weld.weldClassIntrospector is missing [jboss.deployment.subunit.\"XXXXMLBeanProxyEAR.ear\".\"XXXXMLBeanProxyEJB.jar\".beanmanager]",
              "jboss.naming.context.java.comp.XXXXMLBeanProxyEAR.XXXXMLBeanProxyEJB.JVTOrderManagementSessionWS.InstanceName is missing [jboss.naming.context.java.comp.XXXXMLBeanProxyEAR.XXXXMLBeanProxyEJB.JVTOrderManagementSessionWS]"
          ]
      }
      14:34:16,980 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "XXXXMLBeanProxyEAR.ear" (runtime-name : "XXXXMLBeanProxyEAR.ear")
      14:34:16,982 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
      WFLYCTL0184:    New missing/unsatisfied dependencies:
            service jboss.deployment.subunit."XXXXMLBeanProxyEAR.ear"."XXXXMLBeanProxyEJB.jar".beanmanager (missing) dependents: [service jboss.deployment.subunit."XXXXMLBeanProxyEAR.ear"."XXXXMLBeanProxyEJB.jar".weld.weldClassIntrospector, service jboss.deployment.subunit."XXXXMLBeanProxyEAR.ear"."XXXXMLBeanProxyEJB.jar".batch.environment]
            service jboss.deployment.subunit."XXXXMLBeanProxyEAR.ear"."XXXXMLBeanProxyEJB.jar".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."XXXXMLBeanProxyEAR.ear".deploymentCompleteService]
            service jboss.deployment.subunit."XXXXMLBeanProxyEAR.ear"."XXXXMLBeanProxyEJB.jar".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."XXXXMLBeanProxyEAR.ear".WeldStartService]
            service jboss.naming.context.java.comp.XXXXMLBeanProxyEAR.XXXXMLBeanProxyEJB.JVTOrderManagementSessionWS (missing) dependents: [service jboss.naming.context.java.comp.XXXXMLBeanProxyEAR.XXXXMLBeanProxyEJB.JVTOrderManagementSessionWS.InstanceName, service jboss.naming.context.java.comp.XXXXMLBeanProxyEAR.XXXXMLBeanProxyEJB.JVTOrderManagementSessionWS.InAppClientContainer, service jboss.naming.context.java.comp.XXXXMLBeanProxyEAR.XXXXMLBeanProxyEJB.JVTOrderManagementSessionWS.ValidatorFactory, service jboss.naming.context.java.comp.XXXXMLBeanProxyEAR.XXXXMLBeanProxyEJB.JVTOrderManagementSessionWS.Validator]
      WFLYCTL0186:   Services which failed to start:      service jboss.deployment.subunit."XXXXMLBeanProxyEAR.ear"."XXXXMLBeanProxyEJB.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."XXXXMLBeanProxyEAR.ear"."XXXXMLBeanProxyEJB.jar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment "XXXXMLBeanProxyEJB.jar" of deployment "XXXXMLBeanProxyEAR.ear"
      
      14:34:17,349 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
      14:34:17,350 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
      14:34:17,350 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) started (with errors) in 12065ms - Started 358 of 659 services (11 services failed or missing dependencies, 386 services are lazy, passive or on-demand)
      14:34:17,422 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0208: Stopped subdeployment (runtime-name: XXXXMLBeanProxyEJB.jar) in 36ms
      14:34:17,448 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment XXXXMLBeanProxyEAR.ear (runtime-name: XXXXMLBeanProxyEAR.ear) in 63ms
      14:34:17,572 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Undeployed "XXXXMLBeanProxyEAR.ear" (runtime-name: "XXXXMLBeanProxyEAR.ear")
      14:34:17,575 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Service status report
      WFLYCTL0184:    New missing/unsatisfied dependencies:
            service jboss.deployment.unit."XXXXMLBeanProxyEAR.ear".WeldBootstrapService (missing) dependents: [service jboss.deployment.unit."XXXXMLBeanProxyEAR.ear".CdiValidatorFactoryService, service jboss.deployment.unit."XXXXMLBeanProxyEAR.ear".WeldStartService]
            service jboss.deployment.unit."XXXXMLBeanProxyEAR.ear".WeldStartService (missing) dependents: [service jboss.deployment.unit."XXXXMLBeanProxyEAR.ear".CdiValidatorFactoryService]
            service jboss.deployment.unit."XXXXMLBeanProxyEAR.ear".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."XXXXMLBeanProxyEAR.ear".WeldStartService]
      WFLYCTL0186:   Services which failed to start:      service jboss.deployment.subunit."XXXXMLBeanProxyEAR.ear"."XXXXMLBeanProxyEJB.jar".INSTALL
      
      14:34:22,040 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found XXXXMLBeanProxyEAR.ear in deployment directory. To trigger deployment create a file called XXXXMLBeanProxyEAR.ear.dodeploy
      

       

      So then I tried adding the commented out line of "xmlschema-core-2.2.2.jar" to the module to rectify the problem

       

      And then I get this exception:

      14:43:33,271 INFO  [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-6) Creating Service {http://XXX.utility.mycompany.net/}JVTOrderManagementSessionService from class net.mycompany.utility.XXX.JVTOrderManagementSessionWS
      14:43:33,410 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.subunit."XXXXMLBeanProxyEAR.ear"."XXXXMLBeanProxyEJB.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."XXXXMLBeanProxyEAR.ear"."XXXXMLBeanProxyEJB.jar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment "XXXXMLBeanProxyEJB.jar" of deployment "XXXXMLBeanProxyEAR.ear"
       at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
       at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
       at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
       at java.lang.Thread.run(Thread.java:745)
      Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/modules/ModuleClassLoader) previously initiated loading for a different type with name "org/apache/ws/commons/schema/XmlSchemaCollection"
       at org.apache.cxf.xmlbeans.XmlBeansSchemaInitializer.<init>(XmlBeansSchemaInitializer.java:111)
       at org.apache.cxf.xmlbeans.XmlBeansDataBinding.initialize(XmlBeansDataBinding.java:114)
       at org.apache.cxf.service.factory.AbstractServiceFactoryBean.initializeDataBindings(AbstractServiceFactoryBean.java:86)
       at org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:467)
       at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFromClass(JaxWsServiceFactoryBean.java:696)
       at org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:527)
       at org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:261)
       at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:199)
       at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:102)
       at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:168)
       at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:211)
       at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:460)
       at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:338)
       at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:79)
       at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:255)
       at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:543)
       at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:234)
       at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:97)
       at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:59)
       at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73)
       at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
       ... 5 more
      

       

      Which is likely caused by the fact that the CXF jar cxf-core-3.1.4.redhat-1.jar bundled with JBoss with following path:
      C:\jboss-eap-7.0\modules\system\layers\base\org\apache\cxf\main\cxf-core-3.1.4.redhat-1.jar\org\apache\cxf\common\xmlschema\

       

      Also has a SchemaCollection.class

       

      So I'm basically going around and around in a circle here.  I do see that in

      C:\jboss-eap-7.0\modules\system\layers\base\org\apache\cxf\impl\main\

       

      Theres also some other databinding jars of:

      cxf-rt-databinding-aegis-3.1.4.redhat-1.jar

      cxf-rt-databinding-jaxb-3.1.4.redhat-1.jar

       

      But alas no xmlbeans databinding jar.  I have a feeling if I just add the "cxf-rt-databinding-xmlbeans-3.1.6.jar" to that same folder path and to the module.xml - I'll still get the "XmlSchemaException" error.

       

      Does anyone have any recommendations as to what to try next?  I can try bundling CXF 3.1.4 with my EJB project but I'm not 100% sure as to which jars to include.  I'm also not 100% sure in EAP 7 how to exclude the webservice subsystem if need be.

       

      Thoughts, questions concerns and comments are very greatly appreciated!  Thank you!

       

      Jay

       

      Message was edited by: Jason Glass as syntax highlighting often doesnt work when initial discussion is started