You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Glen Mazza <gl...@gmail.com> on 2008/12/19 04:43:00 UTC
Re: Name that Web Service
Just to elaborate a bit on this point--I'm looking at StrikeIron's Zip Code
service[1], if you scroll to the wsdl:service section at the bottom you will
notice four ports within it:
a.) A SOAP 1.0 binding
b.) A SOAP 1.2 binding
c.) HTTP/GET binding
d.) HTTP/POST binding
I can see how CXF can handle (a) and (b), but if I wanted to access the web
service via (c) or (d), would the Dispatch interface help me? Or any of
Sergey's REST work? Just curious.
Thanks,
Glen
[1] http://wslite.strikeiron.com/zipcodeinfolite01/ZIPCodeInfoLite.asmx?WSDL
dkulp wrote:
>
>
> Glen,
>
> If you check the WSDL 1.1 spec, it defines bindings for a special HTTP
> GET/POST binding in addition to SOAP. It's a bit complicated so very
> few toolkits support it. It defines some things like mapping GET
> params to input parts, mapping from FORM data, etc...
>
> Dan
> (sent from my new Mac. :-)
>
>
> Glen Mazza wrote:
>> Hello,
>>
>> I'm looking at a rather older WSDL and am not sure what type of web
>> service
>> it is--RPC/encoded? JAX-RPC? or XML over HTTP JAX-WS or? Here are a
>> couple
>> of its operations below--if anyone could give me a name for this type of
>> web
>> service it would be appreciated.
>>
>> Regards,
>> Glen
>>
>> <wsdl:binding name="FOOHttpPost" type="tns:FOOHttpPost">
>> <http:binding verb="POST"/>
>> <wsdl:operation name="get_foo_date">
>> <http:operation location="/get_foo_date"/>
>> <wsdl:input>
>> <mime:content type="application/x-www-form-urlencoded"/>
>> </wsdl:input>
>> <wsdl:output>
>> <mime:mimeXml part="Body"/>
>> </wsdl:output>
>> </wsdl:operation>
>> <wsdl:operation name="get_bar_data">
>> <http:operation location="/get_bar_data"/>
>> <wsdl:input>
>> <mime:content type="application/x-www-form-urlencoded"/>
>> </wsdl:input>
>> <wsdl:output>
>> <mime:mimeXml part="Body"/>
>> </wsdl:output>
>> </wsdl:operation>
>> </wsdl:binding>
>>
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
>
--
View this message in context: http://www.nabble.com/Name-that-Web-Service-tp16993337p21085324.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Name that Web Service
Posted by Sergey Beryozkin <se...@progress.com>.
Hi
>
> Just to elaborate a bit on this point--I'm looking at StrikeIron's Zip Code
> service[1], if you scroll to the wsdl:service section at the bottom you will
> notice four ports within it:
>
> a.) A SOAP 1.0 binding
> b.) A SOAP 1.2 binding
> c.) HTTP/GET binding
> d.) HTTP/POST binding
JAXWS Dispatch should indeed help you with c. and d. We don't have a JAXRS client just yet, but you may want to try CXF HttpBinding
client support too.
Cheers, Sergey
>
> I can see how CXF can handle (a) and (b), but if I wanted to access the web
> service via (c) or (d), would the Dispatch interface help me? Or any of
> Sergey's REST work? Just curious.
>
> Thanks,
> Glen
>
> [1] http://wslite.strikeiron.com/zipcodeinfolite01/ZIPCodeInfoLite.asmx?WSDL
>
>
>
> dkulp wrote:
>>
>>
>> Glen,
>>
>> If you check the WSDL 1.1 spec, it defines bindings for a special HTTP
>> GET/POST binding in addition to SOAP. It's a bit complicated so very
>> few toolkits support it. It defines some things like mapping GET
>> params to input parts, mapping from FORM data, etc...
>>
>> Dan
>> (sent from my new Mac. :-)
>>
>>
>> Glen Mazza wrote:
>>> Hello,
>>>
>>> I'm looking at a rather older WSDL and am not sure what type of web
>>> service
>>> it is--RPC/encoded? JAX-RPC? or XML over HTTP JAX-WS or? Here are a
>>> couple
>>> of its operations below--if anyone could give me a name for this type of
>>> web
>>> service it would be appreciated.
>>>
>>> Regards,
>>> Glen
>>>
>>> <wsdl:binding name="FOOHttpPost" type="tns:FOOHttpPost">
>>> <http:binding verb="POST"/>
>>> <wsdl:operation name="get_foo_date">
>>> <http:operation location="/get_foo_date"/>
>>> <wsdl:input>
>>> <mime:content type="application/x-www-form-urlencoded"/>
>>> </wsdl:input>
>>> <wsdl:output>
>>> <mime:mimeXml part="Body"/>
>>> </wsdl:output>
>>> </wsdl:operation>
>>> <wsdl:operation name="get_bar_data">
>>> <http:operation location="/get_bar_data"/>
>>> <wsdl:input>
>>> <mime:content type="application/x-www-form-urlencoded"/>
>>> </wsdl:input>
>>> <wsdl:output>
>>> <mime:mimeXml part="Body"/>
>>> </wsdl:output>
>>> </wsdl:operation>
>>> </wsdl:binding>
>>>
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org
>> http://www.dankulp.com/blog
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Name-that-Web-Service-tp16993337p21085324.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>