I can't use shade - too many problems - tried it for two days.  I'm using
the maven assembler one jar to create the uber-jar for the applet.

This is the listing from the uber jar at <jar root>META-INF/cxf   So it
looks like all the rest are there - maybe I can use the maven unpack on
*cxf*.jar to get all bus-extensions.txt and manipulate them before the
assembler creates the uber jar and it gets signed.

bus-extensions.txt
cxf-extension-addr.fixml
cxf-extension-addr.xml
cxf-extension-http.fixml
cxf-extension-http.xml
cxf-extension-jaxws.fixml
cxf-extension-jaxws.xml
cxf-extension-soap.fixml
cxf-extension-soap.xml
cxf-extension-xml.fixml
cxf-extension-xml.xml
cxf.fixml
cxf-servlet.fixml
cxf-servlet.xml
cxf.xml
java2wsbeans.xml
org.apache.cxf.bus.factory
org.apache.cxf.Logger
osgi

This is the contents of that extensioins file - so I guess this belongs to
cxf-extension-http and it's the last one that the assembler sees and simply
overwrites all others with it.

org.apache.cxf.transport.http.HTTPTransportFactory::true
org.apache.cxf.transport.http.HTTPWSDLExtensionLoader::true
org.apache.cxf.transport.http.policy.HTTPClientAssertionBuilder::true:true
org.apache.cxf.transport.http.policy.HTTPServerAssertionBuilder::true:true
org.apache.cxf.transport.http.policy.NoOpPolicyInterceptorProvider::true:true



--
View this message in context: 
http://cxf.547215.n5.nabble.com/CXF-JAX-WS-Client-without-Spring-tp5720035p5720171.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to