You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Paul Fremantle (JIRA)" <ji...@apache.org> on 2007/04/05 12:31:32 UTC
[jira] Created: (AXIS2-2476) Generated WSDL does not implement the
Microsoft rules on wrapping
Generated WSDL does not implement the Microsoft rules on wrapping
-----------------------------------------------------------------
Key: AXIS2-2476
URL: https://issues.apache.org/jira/browse/AXIS2-2476
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [jira] Commented: (AXIS2-2476) Generated WSDL does not implement the Microsoft rules on wrapping
Posted by Paul Fremantle <pz...@gmail.com>.
Angel
Sorry I didn't spot that!!
Paul
On 4/5/07, Angel Todorov <at...@gmail.com> wrote:
> Please take a look at :
>
> https://issues.apache.org/jira/browse/AXIS2-2175
>
> I have already provided a fix for this issue, but noone has considered
> it. Thanks.
>
> Regards,
> Angel
>
> On 4/5/07, Deepal Jayasinghe (JIRA) <ji...@apache.org> wrote:
> >
> > [ https://issues.apache.org/jira/browse/AXIS2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486920 ]
> >
> > 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: https://issues.apache.org/jira/browse/AXIS2-2476
> > > 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: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [jira] Commented: (AXIS2-2476) Generated WSDL does not implement the Microsoft rules on wrapping
Posted by Angel Todorov <at...@gmail.com>.
Please take a look at :
https://issues.apache.org/jira/browse/AXIS2-2175
I have already provided a fix for this issue, but noone has considered
it. Thanks.
Regards,
Angel
On 4/5/07, Deepal Jayasinghe (JIRA) <ji...@apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/AXIS2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486920 ]
>
> 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: https://issues.apache.org/jira/browse/AXIS2-2476
> > 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: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2476) Generated WSDL does not implement the
Microsoft rules on wrapping
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-2476:
------------------------------------
Assignee: Deepal Jayasinghe
> Generated WSDL does not implement the Microsoft rules on wrapping
> -----------------------------------------------------------------
>
> Key: AXIS2-2476
> URL: https://issues.apache.org/jira/browse/AXIS2-2476
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Reporter: Paul Fremantle
> Assignee: Deepal Jayasinghe
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2476) Generated WSDL does not implement the
Microsoft rules on wrapping
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe updated AXIS2-2476:
-------------------------------------
Priority: Blocker (was: Major)
Fix Version/s: 1.3
We need to fix the namespace issue.
> Generated WSDL does not implement the Microsoft rules on wrapping
> -----------------------------------------------------------------
>
> Key: AXIS2-2476
> URL: https://issues.apache.org/jira/browse/AXIS2-2476
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Reporter: Paul Fremantle
> Assignee: Deepal Jayasinghe
> Priority: Blocker
> Fix For: 1.3
>
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2476) Generated WSDL does not implement
the Microsoft rules on wrapping
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486920 ]
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: https://issues.apache.org/jira/browse/AXIS2-2476
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2476) Generated WSDL does not implement
the Microsoft rules on wrapping
Posted by "Paul Fremantle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486911 ]
Paul Fremantle commented on AXIS2-2476:
---------------------------------------
I forgot to mention.... they do support our WSDLs as-is, but they generate much simpler clients when these problems are fixed.
> Generated WSDL does not implement the Microsoft rules on wrapping
> -----------------------------------------------------------------
>
> Key: AXIS2-2476
> URL: https://issues.apache.org/jira/browse/AXIS2-2476
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2476) Generated WSDL does not implement the
Microsoft rules on wrapping
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe resolved AXIS2-2476.
--------------------------------------
Resolution: Fixed
Hi Paul ,
I fixed the issue in the current SVN , I think you will help me by checking whether I have done the right thing.
Thanks
Deepal
> Generated WSDL does not implement the Microsoft rules on wrapping
> -----------------------------------------------------------------
>
> Key: AXIS2-2476
> URL: https://issues.apache.org/jira/browse/AXIS2-2476
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Reporter: Paul Fremantle
> Assignee: Deepal Jayasinghe
> Priority: Blocker
> Fix For: 1.3
>
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org