What kind of Web Service is this?

[stevecoh1]

I am trying to develop client code for a vendor-provided service of a
type I've never seen before.  The vendor does not provide a WSDL, but
they do provide an XSD schema definition, a URL, and a protocol document
in which it is explained that the request parameters are provided as
query parameters appended to the URL itself ?key1="value"&key2="value",
etc.  The XSD does not define a request packet but it does define the
response packet.

Is there a name for this type of Web Service?  (Is it even considered a
Web Service?)  And are there facilities in CXF (or other systems) for
generating client code based on it?  Or am I better off just writing my
own parsers for the response?

[Sergey Beryozkin-2]

Hi

it's a pure HTTP service, and in CXF you can write a code which can consume it using the http/restful client api [1], ex :

WebClient client = WebClient.createClient(http://service);
SomeResponse response = client.query("key1", "value").query("key2", "value").get(SomeResponse.class);

where SomeResponse.class has been generated from the schema.
We do not yet provide the tools for generating the client code (it is on the map though I'm not sure the new tool will make it into
2.3) though but I'm hoping you can get the classes generated from the schema with the help of the xsd plugin....

cheers, Sergey

[1] http://cxf.apache.org/docs/jax-rs.html#JAX-RS-HTTPcentricclients


----- Original Message -----
From: "Steve Cohen" <scohen@...>
To: <users@...>
Sent: Monday, November 02, 2009 4:43 PM
Subject: What kind of Web Service is this?

>I am trying to develop client code for a vendor-provided service of a
> type I've never seen before.  The vendor does not provide a WSDL, but
> they do provide an XSD schema definition, a URL, and a protocol document
> in which it is explained that the request parameters are provided as
> query parameters appended to the URL itself ?key1="value"&key2="value",
> etc.  The XSD does not define a request packet but it does define the
> response packet.
>
> Is there a name for this type of Web Service?  (Is it even considered a
> Web Service?)  And are there facilities in CXF (or other systems) for
> generating client code based on it?  Or am I better off just writing my
> own parsers for the response?
>

[stevecoh1]

Can you point me to information detailing the usage of the xsd plugin?  
Where to find, etc.

Sergey Beryozkin wrote:

> Hi
>
> it's a pure HTTP service, and in CXF you can write a code which can
> consume it using the http/restful client api [1], ex :
>
> WebClient client = WebClient.createClient(http://service);
> SomeResponse response = client.query("key1", "value").query("key2",
> "value").get(SomeResponse.class);
>
> where SomeResponse.class has been generated from the schema.
> We do not yet provide the tools for generating the client code (it is
> on the map though I'm not sure the new tool will make it into 2.3)
> though but I'm hoping you can get the classes generated from the
> schema with the help of the xsd plugin....
>
> cheers, Sergey
>
> [1] http://cxf.apache.org/docs/jax-rs.html#JAX-RS-HTTPcentricclients
>
>
> ----- Original Message ----- From: "Steve Cohen" <scohen@...>
> To: <users@...>
> Sent: Monday, November 02, 2009 4:43 PM
> Subject: What kind of Web Service is this?
>
>
>> I am trying to develop client code for a vendor-provided service of a
>> type I've never seen before.  The vendor does not provide a WSDL, but
>> they do provide an XSD schema definition, a URL, and a protocol document
>> in which it is explained that the request parameters are provided as
>> query parameters appended to the URL itself ?key1="value"&key2="value",
>> etc.  The XSD does not define a request packet but it does define the
>> response packet.
>>
>> Is there a name for this type of Web Service?  (Is it even considered a
>> Web Service?)  And are there facilities in CXF (or other systems) for
>> generating client code based on it?  Or am I better off just writing my
>> own parsers for the response?
>>
>
>
>

Can you point me to information detailing the user of the xsd plugin?

[Sergey Beryozkin-2]

This pom shows how it (cxf-common-xsd) can be used

https://svn.apache.org/repos/asf/cxf/trunk/rt/databinding/jaxb/pom.xml

hope it helps, Sergey

----- Original Message -----
From: "Steve Cohen" <scohen@...>
To: <users@...>
Sent: Monday, November 02, 2009 5:44 PM
Subject: Re: What kind of Web Service is this?

> Can you point me to information detailing the usage of the xsd plugin?  
> Where to find, etc.
>
> Sergey Beryozkin wrote:
>> Hi
>>
>> it's a pure HTTP service, and in CXF you can write a code which can
>> consume it using the http/restful client api [1], ex :
>>
>> WebClient client = WebClient.createClient(http://service);
>> SomeResponse response = client.query("key1", "value").query("key2",
>> "value").get(SomeResponse.class);
>>
>> where SomeResponse.class has been generated from the schema.
>> We do not yet provide the tools for generating the client code (it is
>> on the map though I'm not sure the new tool will make it into 2.3)
>> though but I'm hoping you can get the classes generated from the
>> schema with the help of the xsd plugin....
>>
>> cheers, Sergey
>>
>> [1] http://cxf.apache.org/docs/jax-rs.html#JAX-RS-HTTPcentricclients
>>
>>
>> ----- Original Message ----- From: "Steve Cohen" <scohen@...>
>> To: <users@...>
>> Sent: Monday, November 02, 2009 4:43 PM
>> Subject: What kind of Web Service is this?
>>
>>
>>> I am trying to develop client code for a vendor-provided service of a
>>> type I've never seen before.  The vendor does not provide a WSDL, but
>>> they do provide an XSD schema definition, a URL, and a protocol document
>>> in which it is explained that the request parameters are provided as
>>> query parameters appended to the URL itself ?key1="value"&key2="value",
>>> etc.  The XSD does not define a request packet but it does define the
>>> response packet.
>>>
>>> Is there a name for this type of Web Service?  (Is it even considered a
>>> Web Service?)  And are there facilities in CXF (or other systems) for
>>> generating client code based on it?  Or am I better off just writing my
>>> own parsers for the response?
>>>
>>
>>
>>
> Can you point me to information detailing the user of the xsd plugin?