Re: _at_Representation

From: Marc Hadley <Marc.Hadley_at_Sun.COM>
Date: Thu, 26 Apr 2007 11:15:08 -0400

On Apr 26, 2007, at 10:18 AM, Jerome Louvel wrote:
> The GET method is a special case method. There would be no direct
> handling
> like for post(), put() or delete(). It is useful to take into
> account the
> content negotation and caching. By default, no get() method would be
> necessary but the presence of a @Representation annotation on a get*()
> method would expose one set of representation for the current
> resource. You
> could have on the same resource class:
> @Representation
> Customer getCustomer(){...}
> @Representation
> Document getCustomerAsXml(){...}
> @Representation(mediaType="application/xml")
> InputStream toXml(){...}
So in your proposition @Representation marks a method as servicing a
GET request ? Or could it also be used on put, post, delete, ...
methods ? E.g.

InputStream delete() {...}


Marc Hadley <marc.hadley at>
CTO Office, Sun Microsystems.