Hi Andrew,
The behavior I'm seeing can also be seen in the "simple" example.
If the schema is defined as a single simple-type element, the generated
operation method has no parameters. I have to manually add a String
parameter to the method afterwards:
<xsd:element name="FirstOperation" type="xsd:string" />
public String firstOperation() throws Exception;
But, If the schema is defined as an anonymous complex-type element, the
operation method will then generate properly with parameters:
<xsd:element name="SecondOperation">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Param1" type="xsd:integer"/>
<xsd:element name="Param2" type="xsd:QName"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
public boolean secondOperation(int param0, QName param1) throws
Exception;
-----Original Message-----
From: Andrew Eberbach [mailto:[EMAIL PROTECTED]
Sent: Friday, October 27, 2006 12:59 PM
To: [email protected]
Subject: Re: message types not checked?
1) The wsdl2java script creates the java "stub" classes and an operation
method in each class, but the method is incomplete. No parameters are
generated in the method signature, even if the wsdl indicates that a
parameter is passed to the operation. Is this the intended design, or
is it up to the developer to fill in the correct parameters in the java
code?
<ame>There should definitely be parameters in the methods. Can you give
an
example of a wsdl that generates methods with no parameters when the
wsdl
specifies parameters?</ame>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
