Hi Arthur - thanks for the response. I will give it a shot and let you know.
Arthur Ryman wrote:
Demetris,
in-out operations have exactly two messages. In this example, there is
an input, but it's encoded in the IRI of the request. That's what the
style attribute specifies. IRI style lets you put the input message on
the IRI.
This is a good test for Woden. Drop the <input> and see if Woden
complains.
-- Arthur
On Wed, May 19, 2010 at 12:35 AM, Demetris <[email protected]
<mailto:[email protected]>> wrote:
Is there any code implementing the example I am refering to below
(http://www.ibm.com/developerworks/webservices/library/ws-restwsdl/)
that is downloadable?
Thanks
Demetris wrote:
Hi all,
in one of the examples wsdl for the REST-based BookList I see
the following:
<wsdl:interface name="BookListInterface">
<wsdl:operation name="getBookList"
pattern="http://www.w3.org/ns/wsdl/in-out";
style="http://www.w3.org/ns/wsdl/style/iri";
wsdlx:safe="true">
<wsdl:documentation>
This operation returns a list of books.
</wsdl:documentation>
<wsdl:input element="msg:getBookList"/>
<wsdl:output element="msg:bookList"/>
</wsdl:operation>
</wsdl:interface>
If no inputs are required for the particular method I am
assuming that the wsdl:input element
can be left out. Yes? And if the this is a 'set and forget'
method the same would apply
to the wsdl:output element?
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
<mailto:[email protected]>
For additional commands, e-mail: [email protected]
<mailto:[email protected]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
