Why do you want to do that? Is there an actual problem using a proper SOAP stack with all its attendant benefits? If there's a proper abstraction layer on top of the WS access code then the client shouldn't care one way or the other what library is used underneath.
Note that the article linked by Bhagat shows an approach that uses SAAJ, which works on a lower level than APIs like JAX-WS. That means more code to write, and more opportunities to get things wrong.
William Brogden
Author and all-around good cowpoke
Rancher
Joined: Mar 22, 2000
Posts: 12267
1
posted
0
You could always fake a SOAP client if you can get the clear text of a SOAP request to this service as a template and the service is not implementing all the WS-* security bells and whistles.
Your Jersey client would POST a copy of this text with the desired values pasted into the template.