This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
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.