<
| C# | XML |
---|---|---|
| public string[] Vehicle; public string Gruppe; | < Vehicle> |
| public class ListeClass { public string[] COS; } | < Liste>
< /Liste> |
| public class ListeClass { [XmlElement("cos")] public string[] COS; } | - < Liste> < cos>c1< /cos> < cos>c2< /cos> < /Liste> |
return-Customizing | [return: XmlElement(ElementName="Result")] | XmlElement anstelle SoapElement verwenden (wsdl.exe-generiertes SoapElement hat bei Document-Style nicht funktioniert) |
Standard SOAP Message Formats Specified Using WSDL
- http://www.stylusstudio.com/xmldev/200406/post60190.html (style=rpc/document use=encoded/literals)
- http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html
- http://www.informit.com/articles/article.asp?p=345011&rl=1 Beispiele zu Style und Use, Unterschiede
- http://java.sun.com/developer/technicalArticles/xml/jaxrpcpatterns/
Interoperability: There is a natural tendency to expose the programming language object structures through the WSDL when using RPC style and this causes interoperability issues across platforms. To facilitate interoperability, the WS-I Basic Profile limits the use of the encoding (RPC-encoded or document-encoded) and encourages a literal formatting (document-literal or RPC-literal style). Of the two literal styles, some toolkits today like .NET only support document-literal, and if the web service wants to interoperate with service consumers that use such toolkits, document-literal is the natural choice. - http://java.sun.com/developer/technicalArticles/xml/jaxrpcpatterns/index2.html (RPC-Beispiel)
- https://jax-rpc.dev.java.net/ jaxrpc
- xmlns-Attribut im Resonse-Element der SOAP-Message erforderlich bei Document-Style
< unsp:GetCOSListResult xmlns="urn:siemens-hiq8000">
Wir arbeiten mit Software von http://www.campus21.de.
Verantwortlich für angezeigte Daten ist der Webdomain-Eigentümer laut Impressum.