I suggest reading this article whether or not you decide to use castor for object de/serialization...esp if you decide to go the document/literal route.
http://www-106.ibm.com/developerworks/webservices/library/ws-castor/ -bill -----Original Message----- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 22, 2004 12:18 PM To: [EMAIL PROTECTED] Subject: RE: n00b seeking advice I'm with Jim. Good questions! 1- You can use java2wsdl as a shortcut to create your WSDL, but I recommend that you start with WSDL rather than with Java. You have a sample WSDL document to work with. You might also try using a Schema/WSDL wizard tool -- available with XmlSpy, Sonic Stylus, Kodiak OmniOpera, and Cape Clear SOA Editor. IBM has also just donated a set of XML tools, including Schema and WSDL wizards, to the Eclipse project (although I haven't seen the code yet.) 2- Use array types. 3- Follow the rules defined in the WS-I Basic Profile. Always use document/literal. Don't use RPC/encoded or RPC/literal. (.NET does not support RPC/Literal.) Avoid using all Java collection types. Caveat: if you need to interoperate with the scripting SOAP stacks, you'll probably need to use rpc/encoded. Anne -----Original Message----- From: Larry Meadors [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 21, 2004 10:45 PM To: [EMAIL PROTECTED] Subject: n00b seeking advice OK, I am trying to decide how to implement a webservice, and have a few questions. I have implemented one from a wsdl that was given to me, so I am OK with doing that...but now, I need to do another from scratch. I know I can use java2wsdl to create the wsdl once I create the interface that I want to publish. I am assuming that doing that is a reasonable way to go...am I right? (That is the first question.) Next, I am trying to decide if I should use List or array types for methods that return multiple objects. If it were just Java, that would be a no-brainer, I'd use a List, but this is new for me, so what is the more common approach? (Second question!) Finally, what is the best way to go if I want to make it as compatible with everything as possible? That's it...unless anyone wants to provide any other advice. Thanks! Larry This email message and any attachments are confidential to Endeca. If you are not the intended recipient, please notify Endeca immediately -- by replying to this message or by sending an email to: [EMAIL PROTECTED] -- and destroy all copies of this message and any attachments. Thank you.
