Hi,
I am just struggling with the same issue. I am using document literal style
where encoding namespace is invalid and the .Net client (and not only) is
complaining about it.
Any changes I did in the wsdd file didn't lead to the solution, so I also
would like to know if somebody already solved this issue.
Evgeny
"Dovholuk, Clint"
<[EMAIL PROTECTED]
lobalCrossing.com To
> <axis-user@ws.apache.org>
cc
06/23/2005 02:26
PM Subject
soapenc:Array vs minOccurs="0"
maxOccurs="unbounded"
Please respond to
[EMAIL PROTECTED]
he.org
Hello All,
I've searched through the archives but there's so much overlapping of
keywords I can't locate a specific thread that answers this question, so
please forgive me if this has been covered before (and I'm sure it HAS, I
just can't find where).
Is there some special reason why Axis uses the soapenc:Array type instead
of just using minOccurrs/maxOccurs on a complex type (like .NET) on
auto-generated wsdls?
I imagine there must be some fantastic reason and I'd love to know what it
was/is.
Also is there any way to override this functionality? I figured when I
specified the dotnet_soapenc_fix that all the soapenc references would be
subtracted from wsdl... But the soapenc:Array is still used...
Thanks,
-Clint
