Hello,
I haven't seen the entire thread but I doubt something like Apache CXF, or
even Axis 2, would generate broken WS calls. Certainly, SOAP UI isn't the
answer.
I am forever telling people that SOAP UI isn't a complete testing tool,
because in order to thoroughly test a WS, one needs to generate sources
(Ideally using a variety of different clients and languages), and test the
webservice. Why do this? The problem with webservices is that they're just
too complicated, and clients will often interpret the specification in
different ways. This is precisely why people are moving to straight XML
messages ("RESTful") over a transport mechanism such as HTTP or JMS. Indeed,
our XML Gateway product embraces XML over WS, to allow easy integration with
the AR System (because we assume the AR System can send an XML string through
a WS call without getting that wrong!).
Take the WSDL, generate some sources using Apache CXF and test the solution.
That's what a client will be doing.
Or, buy a proper integration product and get the job done quickly, because
time is money!
John
--
http://www.javasystemsolutions.com
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
