[
http://issues.apache.org/jira/browse/AXIS-1936?page=comments#action_63283 ]
Tim K commented on AXIS-1936:
-----------------------------
I cannot post the source, I'm sure my company's legal department would have
something to say about it. Sorry.
But I'm sure this can be reproduced easily by a method like this:
public NamedValue[] login(String a, String b, NamedValue[] options)
throws MyCustomException;
where:
NamedValue
{
String name;
Object value;
// getters + setters
}
MyCustomException extends Exception
{
// some custom int and String fields + getters for them
...
}
> .NET interop problem: generated WSDL should add nillable="true" for
> methodResponReturn type
> -------------------------------------------------------------------------------------------
>
> Key: AXIS-1936
> URL: http://issues.apache.org/jira/browse/AXIS-1936
> Project: Axis
> Type: Bug
> Environment: Axis 1.2RC3 nightly
> Reporter: Tim K
>
> It seems that I have to edit the WSDL generated by java2wsdl in
> wrapped/literal mode by hand to add nillable="true" to
> the response type, like this:
> <element name="loginResponse">
> <complexType>
> <sequence name="loginResponseReturn" type="impl:ArrayOfNamedValue"
> nillable="true"/>
> </complexType>
> </element>
> Java2WSDL doesn't do this by default and .NET will no return a null object
> even though the return value is xsi:nil
> Please see this bug for the WSDL:
> http://issues.apache.org/jira/browse/AXIS-1926
> The link to the attachment is:
> http://issues.apache.org/jira/secure/attachment/19629/RemoteLoginManager.wsdl
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
