This week's book giveaway is in the Web Services forum.
We're giving away four copies of Microservices in Action and have Morgan Bruce & Paulo A. Pereira on-line!
See this thread for details.
Win a copy of Microservices in Action this week in the Web Services forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Devaka Cooray
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Knute Snortum
  • Junilu Lacar
  • paul wheaton
Saloon Keepers:
  • Ganesh Patekar
  • Frits Walraven
  • Tim Moores
  • Ron McLeod
  • Carey Brown
Bartenders:
  • Stephan van Hulst
  • salvin francis
  • Tim Holloway

Excluding jaxb-2.2.5 and using jaxb-impl-2.2.6 in an EAR on EAP 6.4.0  RSS feed

 
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello guys,

for a couple of days i try to configure my jboss-deployment-structure.xml
to use another version of jaxb-imple/jaxb-api in my webservice packaged in an ear/lib.
My main aim is not to change base installation of jboss eap 6.4.0.

I want to solve the problem: https://github.com/javaee/jaxb-v2/issues/890 .

For example for cxf it works but do not work for jaxb.

<jboss-deployment-structure>
<deployment>
<dependencies>
</dependencies>
<exclusions>
<module name="org.apache.cxf"/>
<module name="org.apache.cxf.impl"/>
<module name="javax.xml.bind.api"/>
<module name="com.sun.xml.bind"/>
</exclusions>
</deployment>

<sub-deployment name="my-jboss-webservice.war">
       <dependencies>

       </dependencies>
</sub-deployment>

</jboss-deployment-structure>

I tried also to install jaxb-impl as another module version and added to JBOSS_MODULEPATH

Another configuration of jboss-deployment-structure.xml  do not work also:

<jboss-deployment-structure>
<deployment>
<dependencies>
</dependencies>
<exclusions>
<module name="org.apache.cxf"/>
<module name="org.apache.cxf.impl"/>
<module name="javax.xml.bind.api"/>
<module name="com.sun.xml.bind"/>
</exclusions>
</deployment>

<sub-deployment name="my-jboss-webservice.war">
       <dependencies>
           <module name="javax.xml.bind.api" slot="jaxb-2.2.6"/>
<module name="com.sun.xml.bind" slot="jaxb-2.2.6"/>
       </dependencies>
</sub-deployment>

</jboss-deployment-structure>

Excluding whole webservice subsystem and adding another version was also not succesfull:

<jboss-deployment-structure>
<deployment>
<dependencies>
</dependencies>
<exclude-subsystems>
           <subsystem name="webservices"/>
        </exclude-subsystems>
<exclusions>
<module name="org.apache.cxf"/>
<module name="org.apache.cxf.impl"/>
<module name="javax.xml.bind.api"/>
<module name="com.sun.xml.bind"/>
</exclusions>
</deployment>

<sub-deployment name="my-jboss-webservice.war">
       <dependencies>
            <module name="org.jboss.as.webservices" slot="jaxb-2.2.6"/>
       </dependencies>
</sub-deployment>

</jboss-deployment-structure>

I tried more configurations but it works only if i directly change the jars(jboss-eap-6.4\modules\system\layers\base\com\sun\xml\bind\main) in the jboss installation.

Can somebody help me with this problem?

Regards
Gary
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!