What you are referring to are called extensibility elements. To the best of my
knowledge, the XML-RPC community has not defined any extensibility elements for
XML-RPC messaging. You are correct WRT where SOAP specific stuff shows up (though you
missed service). One could define extensibilty elements to map messages and operations
to COM, CORBA, DCE-RPC, or any other mechanism.
-----Original Message-----
From: Thalis A. Kalfigopoulos [mailto:[EMAIL PROTECTED]]
Sent: Fri 4/12/2002 3:26 PM
To: [EMAIL PROTECTED]
Cc:
Subject: Newbie WSDL/XML-RPC question
Ignore if I'm off topic (which I am a little bit :). In a WSDL file from the
BWS book I see that the only SOAP specific parts come in at the <binding> and the
<port> elements:
<binding><soap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http";>...<soap:operation soapAction=""/>...
<port...><soap:address...>
From my understanding SOAP is just one XML protocol. One could have used for
example the older XML-RPC. What are the changes need to be made in that case then? Can
anyone point to a WSDL example that binds to an xml-rpc service. Am I missing
something?
TIA,
thalis
