axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ankit Shivankar (JIRA)" <>
Subject [jira] [Commented] (AXIS2-3300) minOccurs="0" always generated by Java2WSDL - problems with .NET client generation
Date Fri, 04 May 2012 05:29:50 GMT


Ankit Shivankar commented on AXIS2-3300:


i am facing a problem when  i am trying to use java/axis web services into
.net .
I always get null response from services.

i find below link , i think i am facing same problem , i am getting all
methods twice.<

I am using Below URL Webservice in .net project.
kindly help me on this .

*Thank you,*

Ankit Shivankar |Software Engineer (.Net)
 Mob. 97700-50317 | <> |India

> minOccurs="0" always generated by Java2WSDL - problems with .NET client generation
> ----------------------------------------------------------------------------------
>                 Key: AXIS2-3300
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.3
>            Reporter: Mauro Molinari
>            Assignee: Deepal Jayasinghe
>             Fix For: 1.7.0, nightly
>         Attachments: axis2-1.4.1.diff
> When you try to expose a POJO as a webservice, suppose you have two Java methods with
the following signatures:
> public Integer a(String, Integer)
> public String b(Integer, String) 
> Java2WSDL adds the minOccurs="0" for each element of each complex type, both for the
input parameters and for the output parameters. 
> When generating clients using .NET WebService Studio 2.0, the result is the following:
> - all the generated C# methods input parameters are doubled, except for the string ones:
the doubled parameters are booleans whose meaning is: "is the previous parameter specified
or not?"
> - all the generated C# methods return parameters are void, except for the string ones
> The actual result are clients with methods like these:
> public void a(string, int, bool);
> public string b(int, bool, string);
> This is obviously a problem, particularly for the "void" return type.
> If I remove minOccurs="0", clients are generated correctly by .NET WebService Studio
> The issue is this: why does Java2WSDL always adds minOccurs="0"? If its meaning were
"it can be null", I think nillable="true" attribute should be more appropriate... Moreover,
if I substitute Integer with int in the original Java class methods, minOccurs="0" is still
added by Java2WSDL, even if an int cannot be null.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message