We currently use exception mappers, but I ran across an odd case. We work as a
proxy to other systems, so if we get back a poorly formed response, we have an
exception mapper for JAXBUnmarshalException. The problem is, if somebody sends
in (to us) a poorly formatted request, it also hits our m
I would catch the upstream and handle it within code.
On 4/23/2014 3:36 PM, Tom Butt wrote:
> We currently use exception mappers, but I ran across an odd case. We work as
> a proxy to other systems, so if we get back a poorly formed response, we have
> an exception mapper for JAXB
I currently have a resource that consumes "application/xml", but I'm moving to
custom media types for versioning. So, the issue happens in marshal/unmarshal
as the root element is the same for both. I have a messagebodyreader/writer to
handle the custom media types in place, and it works well.
g application/xml in my
MessageBodyReader and pivoting in the "isReadable" method on the media type and
the *type*.
-Tom
- Original Message -
From: "John D. Ament"
To: "Tom Butt"
Cc: resteasy-users@lists.sourceforge.net
Sent: Tuesday, July 15, 2014 10:37:
We use the ProxyFactory to create clients in resteasy and typically define
interfaces as:
@GET
@Path("/{id}")
@Produces("application/xml")
ClientResponse getDataByTitle(@PathParam("id") String id,
@QueryParam(value = "title") String name);
or similar.
I need to consume a multip
tipartoutput.addFormData("file", inputStream,
MEDIA_TYPE.APPLICATION_OCTET_STREAM_TYPE);
when I add it to the data to send off.
-Tom
- Original Message -
> From: "William Antônio Siqueira"
> To: "Tom Butt"
> Cc: resteasy-users@lists.sour
s seems to be working as I
hoped now.
-Tom
----- Original Message -
> From: "Tom Butt"
> To: "william fatecsjc"
> Cc: resteasy-users@lists.sourceforge.net
> Sent: Friday, January 16, 2015 10:54:37 AM
> Subject: Re: [Resteasy-users] client for multipart/form-d
