> The original architect specified that the objects should be passed in as > XML instead of objects to support a non-Java SOAP service implementations.
Well, one of SOAP's key features is the ability to pass around objects (actually data structures) in an interoperable manner. > It seems to me that I should just publish the generated WSDL to the service > implementors and that should be sufficient for them to implement the > service in any language. Is that the correct way to do this? I'd say so. If the Java objects that you pass around are simple JavaBeans, Apache's build-in (assuming you're using apache-soap) beanserializer can do all the hard lifting for you. > It also > appears that using XML inputs (vs. objects) hampers discovery of services > in a UDDI repository. No idea. -john > Thanks, > Shawn. > > > This communication is for informational purposes only. It is not intended as > an offer or solicitation for the purchase or sale of any financial instrument > or as an official confirmation of any transaction. All market prices, data > and other information are not warranted as to completeness or accuracy and > are subject to change without notice. Any comments or statements made herein > do not necessarily reflect those of J.P. Morgan Chase & Co., its > subsidiaries and affiliates. > >
