axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Angel Todorov" <>
Subject Re: [jira] Commented: (AXIS2-2476) Generated WSDL does not implement the Microsoft rules on wrapping
Date Thu, 05 Apr 2007 11:11:21 GMT
Please take a look at :

I have already provided a fix for this issue, but noone has considered
it. Thanks.


On 4/5/07, Deepal Jayasinghe (JIRA) <> wrote:
>     [
> Deepal Jayasinghe commented on AXIS2-2476:
> ------------------------------------------
> Hi Paul;
> When we go to last MS interop I also faced that same issue and discuss with MS guys.
At that time they also agree that it is an issue in their side (rather limitation).  That
is why I did not brother to fix that .
> I agree with you that considering interoperability issues , it is good idea to change
Axis2 to work  with MS then we can find our issues and fix them.
> Thanks
> Deepal
> > Generated WSDL does not implement the Microsoft rules on wrapping
> > -----------------------------------------------------------------
> >
> >                 Key: AXIS2-2476
> >                 URL:
> >             Project: Axis 2.0 (Axis2)
> >          Issue Type: Improvement
> >            Reporter: Paul Fremantle
> >
> > Unfortunately the WSDL that Axis2 generates is not "picked up" as doc/lit WRAPPED
by the Microsoft svcutil tool.
> > The reasons are pretty minor. My personal preference would be that Microsoft should
fix these, but given that we want Axis2 to interoperate as well as possible I propose that
we change these.
> > 1) WCF svcutil looks at the names of the generated parts. We generate "part1" but
svcutil is looking for the part name "parameters". Dumb huh! I have reported this to Microsoft.
I propose we also generate the part name "parameters" since its a simple fix.
> > 2) WCF svcutil expects the target namespace of the wrapper element to match the
target namespace of the WSDL. Frankly I don't understand this either since it doesn't affect
the messages on the wire, but here is the comment they produce:
> >     // CODEGEN: Generating message contract since the wrapper namespace (http://sample/xsd)
of message getProfileRequest does not match the default value (http://sample)
> > Currently we produce different namespaces - e.g. http://sample for the WSDL and
http://sample/xsd for the schema. I propose we also change this to improve interop despite
where the blame lies!!!
> > I propose we stop appending /xsd since I think it looks ugly :-)
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message