Paul, The first two items are really problems in the way the SOAP standard is interpreted. The SOAP spec makes it optional to send type info for encoded parameters, such as input parameters in a SOAP request or the return type of a SOAP response. Therefore, if one implementation assumes type info it might not work on another implementation that does'nt. Also, the spec is unclear on how the void type in an RPC based SOAP response should be represented. It could be represented as an empty SOAP envelope or an empty SOAP method response element. Not all implementations support both.
Regards, ________________________________ Harry J. Kobetitsch UBS Warburg One North Wacker Drive Chicago, Illinois 60606-2809 312-525-5866 [EMAIL PROTECTED] -----Original Message----- From: Paul Andrews [mailto:[EMAIL PROTECTED] Sent: Monday, February 24, 2003 3:42 PM To: [EMAIL PROTECTED] Subject: More java2wsdl questions I've noticed what I think are a few problems with the WSDL that java2wsdl generates (I might well be wrong though, I'm fairly new to WSDL). - If a method is void, I get empty message definitions defined for the return value. - If a method takes no arguments I get an empty message definition for the arguments. - If a class has only one or zero attributes, I still get a <sequence> element in its type definition. e.g.: Abstract public class MyClass { } public interface MyService { ... public MyClass getValue() { ... } public void setValue(MyClass value) { ... } } Generates: ... <complexType abstract="true" name="MyClass"> <sequence/> </complexType> ... <wsdl:message name="setValueResponse"> </wsdl:message> <wsdl:message name="getValueRequest"> </wsdl:message> Visit our website at http://www.ubswarburg.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
