-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
The AS modules that currently set dependencies on cxf module (and on jbossws-cxf-transports-httpserver) are using explicit imports elements for including META-INF and META-INF/cxf. We might need to also include schemas/** too (to be verified if that's already covered by default or not)
[JBWS-3607] Missing import/export of CXF schemas in AS modules
Alessio Soldano
added a comment - See https://community.jboss.org/message/802557#802557 ; basically the user was able to build his spring based cxf bus for an in-container client with a jboss-deployment-structure.xml as follows:
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1"> <deployment> <dependencies> <module name="com.oracle" export="true" /> <module name="com.logibec.parameters" export="true" /> <!-- parameters --> <module name="org.apache.cxf.impl" export="true"> <imports> <include path="META-INF"/> <include path="META-INF/cxf"/> </imports> <exports> <include path="META-INF"/> <include path="META-INF/cxf"/> </exports> </module> <module name="org.apache.cxf" export="true"> <imports> <include path="META-INF"/> <include path="META-INF/cxf"/> </imports> <exports> <include path="META-INF"/> <include path="META-INF/cxf"/> </exports> </module> <module name="org.springframework.spring" export="true"> <imports> <include path="META-INF"/> </imports> <exports> <include path="META-INF"/> </exports> </module> </dependencies> </deployment> </jboss-deployment-structure>
We should figure out how to allow achieving the same by simply setting a dependency on org.jboss.ws.cxf.jbossws-cxf-client module (by properly modifying it and/or its dependencies) and eventually better document this process / scenario.
Alessio Soldano
added a comment - See https://community.jboss.org/message/802557#802557 ; basically the user was able to build his spring based cxf bus for an in-container client with a jboss-deployment-structure.xml as follows:
<jboss-deployment-structure xmlns= "urn:jboss:deployment-structure:1.1" >
<deployment>
<dependencies>
<module name= "com.oracle" export= " true " />
<module name= "com.logibec.parameters" export= " true " /> <!-- parameters -->
<module name= "org.apache.cxf.impl" export= " true " >
<imports>
<include path= "META-INF" />
<include path= "META-INF/cxf" />
</imports>
<exports>
<include path= "META-INF" />
<include path= "META-INF/cxf" />
</exports>
</module>
<module name= "org.apache.cxf" export= " true " >
<imports>
<include path= "META-INF" />
<include path= "META-INF/cxf" />
</imports>
<exports>
<include path= "META-INF" />
<include path= "META-INF/cxf" />
</exports>
</module>
<module name= "org.springframework.spring" export= " true " >
<imports>
<include path= "META-INF" />
</imports>
<exports>
<include path= "META-INF" />
</exports>
</module>
</dependencies>
</deployment>
</jboss-deployment-structure>
We should figure out how to allow achieving the same by simply setting a dependency on org.jboss.ws.cxf.jbossws-cxf-client module (by properly modifying it and/or its dependencies) and eventually better document this process / scenario. 
This can't be solved by tuning the existing module dependencies because the cxf impl is needed by spring in the tccl and we don't want it into the jbossws-cxf-client module.
Added documentation on the suggested approach for dealing with this scenario at: https://docs.jboss.org/author/display/JBWS/JBoss+Modules#JBossModules-SpringbasedincontainerBuscreation