You are right - if you will do a interoperable webservice that deal with other clients (.Net ...) its better to go from the wsdl.
But when i use String, int and so on and i generate a wsdl by java2wsdl, I hope the wsdl i get, depends on the standard spec. for wsdl!???? So there should no problem to use the wsdl by other languages!??? Dont know how it looks with complex datatypes!???? Do you all write your own wsdl by hand???? Tomi -----Ursprüngliche Nachricht----- Von: David Cunningham [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 12. Mai 2004 13:14 An: [EMAIL PROTECTED] Betreff: RE: Best Practices? I disagree, the right way is to start with your WSDL and schema files. If you want any hope of being WS-I compliant or using doc/literal this is your best bet. As soon as you start with an interface, you start dealing Java types that do not correlate to schema types very well. For example, if you use: public List getStuff() or public String[] getStuff(), you will either generate a WSDL file that can't be parsed properly by other consumers (.NET, Glue, etc) or be bound to Java collection types that have no chance of being parsed properly by .Net (without a lot of hacking around). My recommendation, again personal preference, is always give thought to the XML that is going across the wire and what you are trying to send/receive and in what structure. This is especially important when dealing with doc/literal since you are sending a single document over the wire. - david -----Original Message----- From: Dorner Thomas [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 12, 2004 2:03 AM To: '[EMAIL PROTECTED]' Subject: AW: Best Practices? The right way is to write a interface which includes all the Methods your webservice should offer. Then you use java2wsdl to generate your wsdl. You have to correct your parameternames in your auto generated wsdl, cause the the params looks like in0, in1, in2... . Then you use wsdl2java to generate your stub, locator, skeleton, impl and maybe a testclient. Now you can implement and deploy your Service by unsing the addtional generated .wsdd files. Hope this helps you Tomi -----Ursprüngliche Nachricht----- Von: Joe Plautz [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 11. Mai 2004 18:48 An: [EMAIL PROTECTED] Betreff: Best Practices? I'm a newbie looking for guidance in creating WebServices with Axis. I've gone through the documentation backwards and forwards and have come up with me own ways of doing things. I start with a WSDL that I create and use WSDL2Java to generate the code and go from there. What I'm looking for is a best practices because I don't feel confident in the way I am going about it. Do most people start from a WSDL? Do people generate a WSDL from an interface and go from there? Do people just create a class and a WSDD file? Or, do people use JWS files that accept a string and the string contains xml formated text? If there are any sites that cover this information, please forward them on to me. Any help will be appreciated!!! Thanks, Joe Plautz [EMAIL PROTECTED]
