Just a quick updated, I have resolved the issue by adding the jws-2.0 jar to
the deployment ...
<dependency>
<groupId>javax</groupId>
<artifactId>jws</artifactId>
<version>2.0</version>
</dependency>
I know it's not the most elegant solution but I don't know how weblogic
works well enough so don't know how to sure prefer the javax.jws classes but
don't ignore the runtime ones, so my sollution is to just proved the java
runtime classes that it's ignoring.
Cheers,
Dale
--
View this message in context:
http://cxf.547215.n5.nabble.com/Deploying-a-WS-Client-to-weblogic-tp5643425p5644200.html
Sent from the cxf-user mailing list archive at Nabble.com.
