Response.Builder doesn't negotiate content type by default about jersey HOT 6 CLOSED

Reported by [email protected]

from jersey.

[email protected] said:
It is possible to return a response without setting the media type and the
runtime should do the acceptable processing. So if you want to return an error
in a form that is acceptable to the client you can do the following:

@get
@ProduceMime(

{"appliction/xml", "application/json"})
public Response get() { JAXBBean b = new JAXBBean("content"); return Response.status(400).entity(b).build(); }

However! there is a bug when doing the following:

@get
@ProduceMime({"appliction/xml", "application/json"}

)
public Response get()

{ JAXBBean b = new JAXBBean("content"); throw new WebApplicationException( Response.status(400).entity(b).build()); }

The client accept header is ignored. So i need to fix that.

It is also possible to do acceptable processing using the:

Request.selectVariant

but i recommend this only for the case when the developer needs to handle wild
cards or cannot declare the supported media types statically.

IMHO returning an error using 200 (OK) is not the recommended thing to do from a
RESTful perspective. The HTTP error status should be used for error reporting
where appropriate. Using 200 (OK) to report errors limits the uniformity of the
interface and increases the coupling between the client and server.

from jersey.

[email protected] said:
Where possible the content type will ascertained from the accept header and the
matching message body reader associated with the entity of the
WebApplicationException.

from jersey.

Was assigned to jersey-issues

from jersey.

This issue was imported from java.net JIRA JERSEY-37

from jersey.

Marked as fixed on Monday, June 16th 2008, 7:44:27 pm

from jersey.