sorry for the silly question but isn't that example in pojo guide returning a weather object that is a custom object? so, I believe we can return a custom object in pojo type implementation as well, rigth? thank you.
--teo On Tue, Mar 2, 2010 at 7:59 AM, Sandeep Khurana < [email protected]> wrote: > Does anybody have any clue on this end? It could be vague, but nothing > seemed documented for this. > > > > -Sandeep > ------------------------------ > > *From:* Sandeep Khurana [mailto:[email protected]] > *Sent:* Monday, February 22, 2010 2:48 PM > *To:* [email protected] > *Subject:* ADB server side code > > > > I am planning to generate server side code (wsdl2java) from WSDL which was > created from an empty java file (using java2wsdl). I did this because > writing WSDL first is a tedious task. I had a few questions on this > approach: > > 1. Is this approach good over POJO deployment (keeping in mind that I > may have custom classes as return type and as parameters)? How will this > behave if I only use POJO style WS? > 2. Will this solution be interoperable if I use ADB? To be specific, if > the Webservice is consumed by CPP client, then, will I be able to get/set > the custom objects correctly. > 3. How much will this approach be handy if I had Java client consuming > the WS? > > > > In addition, where can we find a new doc over existing databinding > comparisions, the existing is of 2007 (old one > here<http://www.ibm.com/developerworks/webservices/library/ws-java3/> > )? > > > > Thanks in advance. > > Sandeep > > DISCLAIMER ========== This e-mail may contain privileged and confidential > information which is the property of Persistent Systems Ltd. It is intended > only for the use of the individual or entity to which it is addressed. If > you are not the intended recipient, you are not authorized to read, retain, > copy, print, distribute or use this message. If you have received this > communication in error, please notify the sender and delete all copies of > this message. Persistent Systems Ltd. does not accept any liability for > virus infected mails. >
