I am sorry I've missed the discussion, but why have you made minOccurs=1
for null non-primitives? As far as I see it, if a value is null the wsdl
should allow passing it as nill or not passing it at all because:
1) two ways of saying something is null means better interoperability as
if a client does not support one way, it can use the other. I believe
.NET 1.x clients are good example of this.
2) by omitting a value we can make the soap message smaller and thus
increase performance.
Mike
Amila Suriarachchi wrote:
On Thu, Jan 7, 2010 at 4:39 PM, Mauro Molinari
<mauro.molin...@cardinis.com <mailto:mauro.molin...@cardinis.com>> wrote:
Amila Suriarachchi ha scritto:
On Thu, Jan 7, 2010 at 3:35 PM, Mauro Molinari
<mauro.molin...@cardinis.com
<mailto:mauro.molin...@cardinis.com>
<mailto:mauro.molin...@cardinis.com
<mailto:mauro.molin...@cardinis.com>>> wrote:
Amila Suriarachchi ha scritto:
ok then lets make minOccurs = 1 by default. As Sosnoski
has said
it is the the best solution. but that make everyone life
easier.
ohh. this should be 'As Sosnoski has said it is not the the best
solution' :) Sorry for mistake.
thanks,
Amila.
Ok, but... given my last comments on the bug report, what is your
last committed solution then?
Is it:
a) "nothing (=> minOccurs=1, nillable=false)" for primitives and
"nillable=true (=> still minOccurs=1)" for non-primitives
this should be the way.
Amila.
- OR -
b) "nothing (=> minOccurs=1, nillable=false)" in any case
Thanks.
--
Mauro Molinari
Software Designer & Developer
E-mail: mauro.molin...@cardinis.com <mailto:mauro.molin...@cardinis.com>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
