[
https://issues.apache.org/jira/browse/TUSCANY-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503610
]
Matthew Peters commented on TUSCANY-1297:
-----------------------------------------
I realise I have got a problem here - I raised the original JIRA with a title
that presupposed what the problem was. Really the problem is that the WSDL will
not validate with visual studio, soapscope, oXygen, or, I now discover, XERCES.
There appear to be at least two problems:
xsi:type upsets visual studio
the order of the <tns3:xxxx elements upsets XERCES
I assume, though can't be sure, because I have not tried them, that soapscope
and oXygten are upset by the second problem.
So there are two problems with the given WSDL. Are you okay with having them
both in one JIRA or do you want it split into two?
> xsi:type in generated XML causes it not to validate/load into: visual studio
> or Mindreef SOAPscope
> --------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-1297
> URL: https://issues.apache.org/jira/browse/TUSCANY-1297
> Project: Tuscany
> Issue Type: Bug
> Components: C++ SDO
> Affects Versions: Cpp-Next
> Environment: any
> Reporter: Matthew Peters
> Fix For: Cpp-Next
>
>
> We use SDO to build and generate WSDL. We use the standard WSDL and SOAP
> schemas (schemata?) to build the model then add port, operation, binding etc.
> elements, then serialise the lot to XML. There are occasional xsi:type
> attributes in the serialised XML which cause the WSDL not to validate or load
> in visual studio. Here is a snippet from WSDL that we have generated in this
> way:
> <binding name="Labnet_API_LabnetOnline_001_ImplementationBinding"
> type="tns2:Labnet_API_LabnetOnline_001_ImplementationPortType">
> <operation name="getRestorations">
> <input>
> <tns3:body xsi:type="tns3:tBody" use="literal"/>
> </input>
> <output>
> <tns3:body xsi:type="tns3:tBody" use="literal"/>
> </output>
> <tns3:operation xsi:type="tns3:tOperation" soapAction=""/>
> </operation>
> <tns3:binding xsi:type="tns3:tBinding"
> transport="http://schemas.xmlsoap.org/soap/http"; style="document"/>
> </binding>
> These xsi:type attributes cause this WSDL to fail to load. I quote one of our
> users:
> > MS Visual Studio (I'm using Visual Web Dev 2005 Express Edition) will
> > not import a SCA generated WSDL. It complains that it does not validate
> > because of the following element attributes:
> > xsi:type="tns3:tBody" of <tns3:body>
> > xsi:type="tns3:tAddress" of <tns3:address>
> > Stripping out these attributes resolved the VS WSDL import problem.
> and a different bug report but the same problem:
> > WSDL generated does not validate (ran against the oXygen editor and
> Mindreef SOAPscope).
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
