Re: JSR311: MessageBodyWriter.writeTo(., Class, ....)

From: Stephan Koops <>
Date: Wed, 19 Mar 2008 12:41:58 +0100

Sorry for third email, but I've see a problem to what I wrote:
When we ever give the return type of the method, than we have the
problem, that the MessageBodyWriter get sometimes
So it causes trouble, if we giv the result type to the
MessageBodyWriter. A null result also will result in 204 by default.
Because of that I propose to define: If an entity object is null, use no
MessageBodyWriter, and return no message body.
I think, we can remove the Class parameter of
MessageBodyWriter.writeTo(......) and isWriteable(...).
Otherwise it need to be precised, what should happen if the object is null.


Stephan Koops schrieb:
> Hi,
> Bill anounced in issue 36 [1] rightly, that the class is needed to the
> MessageBodyWriter. The argument is, that the returned object may be
> null. This indicates, that the type given to
> MessageBodyWriter.writeTo(., Class, ....) is the return type of the
> resource method.
> The javadoc of MessageBodyWriter.writeTo(., Class, ....) says, that
> the class of the object to be written should be given here.
> If the returned object is a subclass (or implementation) of the
> returned type, this differs.
> Should here ever be the return type of the resource method be given?
> Than you have to conform the javadoc a little bit.
> regards
> Stephan
> [1]
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail: