Re: JSR311: Draft of 1.1 Maintenance Release for review

From: Bill Burke <>
Date: Tue, 27 Jan 2009 16:58:38 -0500

Marc Hadley wrote:
> On Jan 27, 2009, at 10:33 AM, Bill Burke wrote:
>> Initial Comments:
>> * EJB Singletons should be a required integration point as well.
>> Resources need to be able to hold state sometimes.
> It that still a requirement with JSR 299 (the spec formally know as
> WebBeans) in the picture. Wouldn't that enable this anyway ?

I don't know. Does JSR 299 still say EJBs are Web Beans? I think its
safer to require EJB Singletons explicitly in the text.

>> * @OPTIONS should be added as an http method with a default behavior
>> defined.
> You are the second person to request that, see issue 67:
> I recall that we didn't add a @OPTIONS in the first place as we thought
> it wouldn't be used much but I can't see any harm in adding it other
> than cluttering the API a bit. Anyone opposed to adding it ? Either way
> I think we should avoid adding @TRACE or @CONNECT.

What about PATCH, MERGE, WebDav? Does it really hurt to add these too?
  Only thing I can think of is that the introduced methods might have
some default response code semantics that are different than other HTTP

PATCH seems to be gaining momentum and I'd hate for all of us JAX-RS
guys to have our own @PATCH, or worse, each application have its own
version of @PATCH.

Bill Burke
JBoss, a division of Red Hat