[
https://issues.apache.org/jira/browse/TUSCANY-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498562
]
Matthew Peters commented on TUSCANY-1297:
-----------------------------------------
I can post one that shows the same problem that I just generated from one of
our own components. You'll see that tns3 is the soap namespace and yes xsi is
defined. If you want them you'll find the wsdl and soap xsd documents that we
use at http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd and
http://schemas.xmlsoap.org/wsdl/soap/2003-02-11.xsd
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:tns2="http://Greeting"; xmlns:tns="http://schemas.xmlsoap.org/wsdl/";
xmlns:tns3="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
targetNamespace="http://Greeting";>
<types>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema";
targetNamespace="http://Greeting";
elementFormDefault="qualified">
<xs:element name="greet">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="greetResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="greetReturn" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</types>
<message name="greetRequest">
<part name="greetRequest" element="tns2:greet"/>
</message>
<message name="greetResponse">
<part name="return" element="tns2:greetResponse"/>
</message>
<portType name="GreetingPortType">
<operation name="greet">
<input message="tns2:greetRequest"/>
<output message="tns2:greetResponse"/>
</operation>
</portType>
<binding name="GreetingBinding" type="tns2:GreetingPortType">
<operation name="greet">
<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>
<service name="GreetingService">
<port name="GreetingPort" binding="tns2:GreetingBinding">
<tns3:address xsi:type="tns3:tAddress"
location="http://localhost/examples/SCA/helloworldscawsservice/Greeting.php"/>
</port>
</service>
</definitions>
<!-- this line identifies this file as WSDL generated by SCA for PHP. Do not
remove -->
> 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-current
> Environment: any
> Reporter: Matthew Peters
>
> 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]
