axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Amila Suriarachchi <>
Subject Re: [Axis2] making minOccurs=1 by default for wsdl generated with POJO
Date Wed, 06 Jan 2010 04:53:00 GMT
On Tue, Jan 5, 2010 at 8:26 PM, Mauro Molinari

> Mauro Molinari ha scritto:
>  Please note that all my trials and researches were carried out on .NET 1.1
>> and .NET 2.0 interoperability. I don't have details on the behaviours of 3.x
>> .NET client generation tools. Maybe in the later versions all the issues
>> have been solved (so that minOccurs=0 could actually be used with no harm),
>> but there are many .NET 1.1/2.0 users still out there.
> Well, I should be more clear here. As I wrote in the issue:
> using nillable=true is actually the safest way to go if we talk about .NET
> >= 2.0.
> In .NET 1.x, the client generation tools simply ignore nillable=true
> attribute, so minOccurs=0 would be in some way better (if we talk about
> operation input parameters, although the doubled-parameters issue) or worse
> (if we talk about output parameters, i.e.: the void return type problem).
> In the JIRA issue I explained what would be the best solution in my
> opinion, but Amila does not like the idea to have a "compatibility" flag
> just for .NET 1.x, so as a compromise he proposed the use of nillable=true
> at least to avoid the void return type bug and the doubled-parameter
> aesthetic issue.
> In this sense, the nillable=true seems to be the least problematic
> solution, given that .NET 1.x support would still be excluded.

ok then lets make minOccurs = 1 by default. As Sosnoski has said it is the
the best solution. but that make everyone life easier.


> --
> Mauro Molinari
> Software Designer & Developer
> E-mail:

Amila Suriarachchi
WSO2 Inc.

View raw message