a REST response
Hello,
From trying out the sample apps and searching the web I have a pretty good
sense
on how to publish a restful service, but not on how to consume one. My
previous
experience with web services are WSDL based, which are pretty straight forward
for marshaling the xml
Thx. Mark, I appreciate your response. Looking at a REST response from a vendor
who we are trying to link up with, the xml is self describing through a type
attribute (datetime, integer...):
created-at type=datetime2008-10-01T04:45:19Z/created-at
description1/8 UNION/description
id
Hi Stephan,
Currently we are not creating the REST response. Rather we are making calls to a
vendor's REST api.
The response is not going to be readily consumed by a client, which is where I
believe the JSON representation would make sense. We are going to persisted a
representation of the
I think I was missing the forest for the trees on this. I am kind of a framework
junkie, but in hindsight since I am only consuming the rest response I don't
really need restlets at all. Basically I just need to suck the response into a
dom, and then use jaxb with annotations to create the objects
Hi,
buzzterrier wrote:
I think I was missing the forest for the trees on this. I am kind of a framework
junkie, but in hindsight since I am only consuming the rest response I don't
really need restlets at all. Basically I just need to suck the response into a
dom, and then use jaxb
Hello,
From trying out the sample apps and searching the web I have a pretty good
sense
on how to publish a restful service, but not on how to consume one. My previous
experience with web services are WSDL based, which are pretty straight forward
for marshaling the xml into a pojo. But I am not
Good day.
I think your question can reside at a number of different levels, but
I'll take a stab at the simplest and most obvious. Hopefully this
isn't so simple as to be of no use.
Here are a few lines of code from one of my JUnit tests, that acts as
a client doing a GET against a
7 matches
Mail list logo
