You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by Demetris <de...@ece.neu.edu> on 2010/05/02 06:04:10 UTC
Re: Examples
Hi all,
what is (or are) the particular and specific difference between a
SOAP serv WSDL 2.0
description and a REST serv WSDL 2.0 description that will make a parser
(or a flag
setter) distinguish between the two? Would the existance of the keyword
'soap' in the former
case be such an indisputable evidence? The ports may be?
Thanks
>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
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 <demetris@ece.neu.edu
> <ma...@ece.neu.edu>> 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: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Arthur Ryman <ar...@gmail.com>.
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 <de...@ece.neu.edu> 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: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
Sounds good - thanks Arthur.
Arthur Ryman wrote:
> Demetris,
>
> Yes, the WSDL file advertises the available bindings, The client picks the
> best binding for its purposes.
>
> Regards,
> ___________________________________________________________________________
>
> Arthur Ryman, PhD, DE
>
>
> Chief Architect, Project and Portfolio Management
>
> IBM Software, Rational
>
> Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063
> Twitter | Facebook | YouTube
>
>
>
>
>
>
>
> From:
> Demetris <de...@ece.neu.edu>
> To:
> woden-dev@ws.apache.org
> Date:
> 05/03/2010 01:39 PM
> Subject:
> Re: Examples
>
>
>
>
> Hi Arthur and thanks for the response as well - so just as I thought ...
> Axis for example
> uses the WSDL file to generate appropriate stubs for invoking a service
> (based on
> the binding). My pt was along the same lines, that without prior
> knowledge of the remote
> service, parsing the incoming WSDL file the client should be able to
> determine the binding
> type and to take appropriate actions to invoke it - SOAP or REST or
> whatever else.
> Do you agree?
>
> Arthur Ryman wrote:
>
>> Demetris,
>>
>> Sagara is correct. WSDL 2.0 lets you describe a Web service abstractly
>> by defining its <interface>. You then define one or more <binding>s
>> for it to describe the concrete protocol used to invoke it.
>>
>> There is a binding types for SOAP:/ http://www.w3.org/ns/wsdl/soap/
>>
>> REST uses the HTTP binding: /http://www.w3.org/ns/wsdl/http/
>>
>> These are described in Part 2 of the spec. [1]
>>
>> -- Arthur
>>
>> [1] http://www.w3.org/TR/wsdl20-adjuncts/
>>
>> On Mon, May 3, 2010 at 12:56 AM, Demetris <demetris@ece.neu.edu
>> <ma...@ece.neu.edu>> wrote:
>>
>>
>> Hi Sagara,
>>
>> sorry if my original posting was a bit confusing. You are indeed
>> providing some good information below and in fact
>> I am aware of most of it. To say it in simpler terms, if a client
>> is retrieving WSDL files from a set of remote sites
>> without knowing if what they describe is a deployed service is a
>> SOAP service or a REST service, can the
>> client know by inspecting the WSDL document such a type? My
>> feeling (and as you may be suggesting below)
>> that this is not a reliable method to find such a difference as
>> descriptions of these services may yield identical
>> WSDL documents. Is this correct? But I do see that SOAP
>> descriptions usually carry either a SOAPAction
>> or a soap operation tag - is this always the case or not?
>>
>> Thanks again
>>
>> Sagara Gunathunga wrote:
>>
>>
>> I' m not sure what is the exact problem you have here,
>> basically WSDL 2.0 Interface is used to describe abstract
>> interface of a service (contract) and it's common for both
>> SOAP and REST. WSDL 2.0 Binding component describe how to
>> access above interface using a concrete protocol like SOAP ,
>> HTTP etc.
>>
>> Following link [1] describe WSDL 2.0 SOAP 1.1 binding that
>> can be used to provide required details in order to access the
>> service using SAOP 1.1 protocol , WSDL 2.0 HTTP binding [2]
>> describe details required to access the service using HTTP
>> protocol ( REST ) , in WSDL level this is the mechanism to
>> describe REST and SOAP services, I guess this make sense.
>>
>>
>> BTW each WS engine use their own techniques to distinguish
>> SOAP and REST invocations at run time , As an example Axis2
>> basically assume absence of SAOP structure in a incoming
>> message as a REST invocation. But this is not relevant to WSDL
>> description .
>> [1] -
>> http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626/
>> [2] -
>>
>>
> http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626/#http-binding
>
>> Thanks,
>>
>> On Sun, May 2, 2010 at 9:34 AM, Demetris <demetris@ece.neu.edu
>> <ma...@ece.neu.edu> <mailto:demetris@ece.neu.edu
>> <ma...@ece.neu.edu>>> wrote:
>>
>>
>> Hi all,
>>
>> what is (or are) the particular and specific difference
>> between
>> a SOAP serv WSDL 2.0
>> description and a REST serv WSDL 2.0 description that will
>> make a
>> parser (or a flag
>> setter) distinguish between the two? Would the existance of
>>
> the
>
>> keyword 'soap' in the former
>> case be such an indisputable evidence? The ports may be?
>>
>>
>> Thanks
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>>
>> For additional commands, e-mail:
>> woden-dev-help@ws.apache.org <
>>
> mailto:woden-dev-help@ws.apache.org>
>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>
>>
>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/
>> <http://people.apache.org/%7Esagara/>
>> <http://people.apache.org/%7Esagara/>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> For additional commands, e-mail: woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Arthur Ryman <ry...@ca.ibm.com>.
Demetris,
Yes, the WSDL file advertises the available bindings, The client picks the
best binding for its purposes.
Regards,
___________________________________________________________________________
Arthur Ryman, PhD, DE
Chief Architect, Project and Portfolio Management
IBM Software, Rational
Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063
Twitter | Facebook | YouTube
From:
Demetris <de...@ece.neu.edu>
To:
woden-dev@ws.apache.org
Date:
05/03/2010 01:39 PM
Subject:
Re: Examples
Hi Arthur and thanks for the response as well - so just as I thought ...
Axis for example
uses the WSDL file to generate appropriate stubs for invoking a service
(based on
the binding). My pt was along the same lines, that without prior
knowledge of the remote
service, parsing the incoming WSDL file the client should be able to
determine the binding
type and to take appropriate actions to invoke it - SOAP or REST or
whatever else.
Do you agree?
Arthur Ryman wrote:
> Demetris,
>
> Sagara is correct. WSDL 2.0 lets you describe a Web service abstractly
> by defining its <interface>. You then define one or more <binding>s
> for it to describe the concrete protocol used to invoke it.
>
> There is a binding types for SOAP:/ http://www.w3.org/ns/wsdl/soap/
>
> REST uses the HTTP binding: /http://www.w3.org/ns/wsdl/http/
>
> These are described in Part 2 of the spec. [1]
>
> -- Arthur
>
> [1] http://www.w3.org/TR/wsdl20-adjuncts/
>
> On Mon, May 3, 2010 at 12:56 AM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu>> wrote:
>
>
> Hi Sagara,
>
> sorry if my original posting was a bit confusing. You are indeed
> providing some good information below and in fact
> I am aware of most of it. To say it in simpler terms, if a client
> is retrieving WSDL files from a set of remote sites
> without knowing if what they describe is a deployed service is a
> SOAP service or a REST service, can the
> client know by inspecting the WSDL document such a type? My
> feeling (and as you may be suggesting below)
> that this is not a reliable method to find such a difference as
> descriptions of these services may yield identical
> WSDL documents. Is this correct? But I do see that SOAP
> descriptions usually carry either a SOAPAction
> or a soap operation tag - is this always the case or not?
>
> Thanks again
>
> Sagara Gunathunga wrote:
>
>
> I' m not sure what is the exact problem you have here,
> basically WSDL 2.0 Interface is used to describe abstract
> interface of a service (contract) and it's common for both
> SOAP and REST. WSDL 2.0 Binding component describe how to
> access above interface using a concrete protocol like SOAP ,
> HTTP etc.
>
> Following link [1] describe WSDL 2.0 SOAP 1.1 binding that
> can be used to provide required details in order to access the
> service using SAOP 1.1 protocol , WSDL 2.0 HTTP binding [2]
> describe details required to access the service using HTTP
> protocol ( REST ) , in WSDL level this is the mechanism to
> describe REST and SOAP services, I guess this make sense.
>
>
> BTW each WS engine use their own techniques to distinguish
> SOAP and REST invocations at run time , As an example Axis2
> basically assume absence of SAOP structure in a incoming
> message as a REST invocation. But this is not relevant to WSDL
> description .
> [1] -
> http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626/
> [2] -
>
http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626/#http-binding
>
> Thanks,
>
> On Sun, May 2, 2010 at 9:34 AM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>> wrote:
>
>
> Hi all,
>
> what is (or are) the particular and specific difference
> between
> a SOAP serv WSDL 2.0
> description and a REST serv WSDL 2.0 description that will
> make a
> parser (or a flag
> setter) distinguish between the two? Would the existance of
the
> keyword 'soap' in the former
> case be such an indisputable evidence? The ports may be?
>
>
> Thanks
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org <
mailto:woden-dev-help@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
> <http://people.apache.org/%7Esagara/>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
Hi Arthur and thanks for the response as well - so just as I thought ...
Axis for example
uses the WSDL file to generate appropriate stubs for invoking a service
(based on
the binding). My pt was along the same lines, that without prior
knowledge of the remote
service, parsing the incoming WSDL file the client should be able to
determine the binding
type and to take appropriate actions to invoke it - SOAP or REST or
whatever else.
Do you agree?
Arthur Ryman wrote:
> Demetris,
>
> Sagara is correct. WSDL 2.0 lets you describe a Web service abstractly
> by defining its <interface>. You then define one or more <binding>s
> for it to describe the concrete protocol used to invoke it.
>
> There is a binding types for SOAP:/ http://www.w3.org/ns/wsdl/soap/
>
> REST uses the HTTP binding: /http://www.w3.org/ns/wsdl/http/
>
> These are described in Part 2 of the spec. [1]
>
> -- Arthur
>
> [1] http://www.w3.org/TR/wsdl20-adjuncts/
>
> On Mon, May 3, 2010 at 12:56 AM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu>> wrote:
>
>
> Hi Sagara,
>
> sorry if my original posting was a bit confusing. You are indeed
> providing some good information below and in fact
> I am aware of most of it. To say it in simpler terms, if a client
> is retrieving WSDL files from a set of remote sites
> without knowing if what they describe is a deployed service is a
> SOAP service or a REST service, can the
> client know by inspecting the WSDL document such a type? My
> feeling (and as you may be suggesting below)
> that this is not a reliable method to find such a difference as
> descriptions of these services may yield identical
> WSDL documents. Is this correct? But I do see that SOAP
> descriptions usually carry either a SOAPAction
> or a soap operation tag - is this always the case or not?
>
> Thanks again
>
> Sagara Gunathunga wrote:
>
>
> I' m not sure what is the exact problem you have here,
> basically WSDL 2.0 Interface is used to describe abstract
> interface of a service (contract) and it's common for both
> SOAP and REST. WSDL 2.0 Binding component describe how to
> access above interface using a concrete protocol like SOAP ,
> HTTP etc.
>
> Following link [1] describe WSDL 2.0 SOAP 1.1 binding that
> can be used to provide required details in order to access the
> service using SAOP 1.1 protocol , WSDL 2.0 HTTP binding [2]
> describe details required to access the service using HTTP
> protocol ( REST ) , in WSDL level this is the mechanism to
> describe REST and SOAP services, I guess this make sense.
>
>
> BTW each WS engine use their own techniques to distinguish
> SOAP and REST invocations at run time , As an example Axis2
> basically assume absence of SAOP structure in a incoming
> message as a REST invocation. But this is not relevant to WSDL
> description .
> [1] -
> http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626/
> [2] -
> http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626/#http-binding
>
> Thanks,
>
> On Sun, May 2, 2010 at 9:34 AM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>> wrote:
>
>
> Hi all,
>
> what is (or are) the particular and specific difference
> between
> a SOAP serv WSDL 2.0
> description and a REST serv WSDL 2.0 description that will
> make a
> parser (or a flag
> setter) distinguish between the two? Would the existance of the
> keyword 'soap' in the former
> case be such an indisputable evidence? The ports may be?
>
>
> Thanks
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
> <http://people.apache.org/%7Esagara/>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Arthur Ryman <ar...@gmail.com>.
Demetris,
Sagara is correct. WSDL 2.0 lets you describe a Web service abstractly by
defining its <interface>. You then define one or more <binding>s for it to
describe the concrete protocol used to invoke it.
There is a binding types for SOAP:* http://www.w3.org/ns/wsdl/soap*
REST uses the HTTP binding: *http://www.w3.org/ns/wsdl/http*
These are described in Part 2 of the spec. [1]
-- Arthur
[1] http://www.w3.org/TR/wsdl20-adjuncts/
On Mon, May 3, 2010 at 12:56 AM, Demetris <de...@ece.neu.edu> wrote:
>
> Hi Sagara,
>
> sorry if my original posting was a bit confusing. You are indeed providing
> some good information below and in fact
> I am aware of most of it. To say it in simpler terms, if a client is
> retrieving WSDL files from a set of remote sites
> without knowing if what they describe is a deployed service is a SOAP
> service or a REST service, can the
> client know by inspecting the WSDL document such a type? My feeling (and as
> you may be suggesting below)
> that this is not a reliable method to find such a difference as
> descriptions of these services may yield identical
> WSDL documents. Is this correct? But I do see that SOAP descriptions
> usually carry either a SOAPAction
> or a soap operation tag - is this always the case or not?
>
> Thanks again
>
> Sagara Gunathunga wrote:
>
>>
>> I' m not sure what is the exact problem you have here, basically WSDL 2.0
>> Interface is used to describe abstract interface of a service (contract)
>> and it's common for both SOAP and REST. WSDL 2.0 Binding component describe
>> how to access above interface using a concrete protocol like SOAP , HTTP
>> etc.
>>
>> Following link [1] describe WSDL 2.0 SOAP 1.1 binding that can be used to
>> provide required details in order to access the service using SAOP 1.1
>> protocol , WSDL 2.0 HTTP binding [2] describe details required to access
>> the service using HTTP protocol ( REST ) , in WSDL level this is the
>> mechanism to describe REST and SOAP services, I guess this make sense.
>>
>>
>> BTW each WS engine use their own techniques to distinguish SOAP and REST
>> invocations at run time , As an example Axis2 basically assume absence of
>> SAOP structure in a incoming message as a REST invocation. But this is not
>> relevant to WSDL description .
>> [1] - http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626/
>> [2] -
>> http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626/#http-binding
>>
>> Thanks,
>>
>> On Sun, May 2, 2010 at 9:34 AM, Demetris <demetris@ece.neu.edu <mailto:
>> demetris@ece.neu.edu>> wrote:
>>
>>
>> Hi all,
>>
>> what is (or are) the particular and specific difference between
>> a SOAP serv WSDL 2.0
>> description and a REST serv WSDL 2.0 description that will make a
>> parser (or a flag
>> setter) distinguish between the two? Would the existance of the
>> keyword 'soap' in the former
>> case be such an indisputable evidence? The ports may be?
>>
>>
>> Thanks
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>>
>> For additional commands, e-mail: woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>>
>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/><
>> http://people.apache.org/%7Esagara/>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
Hi Sagara,
sorry if my original posting was a bit confusing. You are indeed
providing some good information below and in fact
I am aware of most of it. To say it in simpler terms, if a client is
retrieving WSDL files from a set of remote sites
without knowing if what they describe is a deployed service is a SOAP
service or a REST service, can the
client know by inspecting the WSDL document such a type? My feeling (and
as you may be suggesting below)
that this is not a reliable method to find such a difference as
descriptions of these services may yield identical
WSDL documents. Is this correct? But I do see that SOAP descriptions
usually carry either a SOAPAction
or a soap operation tag - is this always the case or not?
Thanks again
Sagara Gunathunga wrote:
>
> I' m not sure what is the exact problem you have here, basically WSDL
> 2.0 Interface is used to describe abstract interface of a service
> (contract) and it's common for both SOAP and REST. WSDL 2.0 Binding
> component describe how to access above interface using a concrete
> protocol like SOAP , HTTP etc.
>
> Following link [1] describe WSDL 2.0 SOAP 1.1 binding that can be
> used to provide required details in order to access the service using
> SAOP 1.1 protocol , WSDL 2.0 HTTP binding [2] describe details
> required to access the service using HTTP protocol ( REST ) , in
> WSDL level this is the mechanism to describe REST and SOAP services,
> I guess this make sense.
>
>
> BTW each WS engine use their own techniques to distinguish SOAP and
> REST invocations at run time , As an example Axis2 basically assume
> absence of SAOP structure in a incoming message as a REST invocation.
> But this is not relevant to WSDL description .
>
> [1] - http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626/
> [2] - http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626/#http-binding
>
> Thanks,
>
> On Sun, May 2, 2010 at 9:34 AM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu>> wrote:
>
>
> Hi all,
>
> what is (or are) the particular and specific difference between
> a SOAP serv WSDL 2.0
> description and a REST serv WSDL 2.0 description that will make a
> parser (or a flag
> setter) distinguish between the two? Would the existance of the
> keyword 'soap' in the former
> case be such an indisputable evidence? The ports may be?
>
>
> Thanks
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Sagara Gunathunga <sa...@gmail.com>.
I' m not sure what is the exact problem you have here, basically WSDL 2.0
Interface is used to describe abstract interface of a service (contract)
and it's common for both SOAP and REST. WSDL 2.0 Binding component describe
how to access above interface using a concrete protocol like SOAP , HTTP
etc.
Following link [1] describe WSDL 2.0 SOAP 1.1 binding that can be used to
provide required details in order to access the service using SAOP 1.1
protocol , WSDL 2.0 HTTP binding [2] describe details required to access
the service using HTTP protocol ( REST ) , in WSDL level this is the
mechanism to describe REST and SOAP services, I guess this make sense.
BTW each WS engine use their own techniques to distinguish SOAP and REST
invocations at run time , As an example Axis2 basically assume absence of
SAOP structure in a incoming message as a REST invocation. But this is not
relevant to WSDL description .
[1] - http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626/
[2] - http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626/#http-binding
Thanks,
On Sun, May 2, 2010 at 9:34 AM, Demetris <de...@ece.neu.edu> wrote:
>
> Hi all,
>
> what is (or are) the particular and specific difference between a SOAP
> serv WSDL 2.0
> description and a REST serv WSDL 2.0 description that will make a parser
> (or a flag
> setter) distinguish between the two? Would the existance of the keyword
> 'soap' in the former
> case be such an indisputable evidence? The ports may be?
>
>
> Thanks
>
>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/