Re: JSR311: _at_Singleton

From: Marc Hadley <Marc.Hadley_at_Sun.COM>
Date: Wed, 11 Jun 2008 10:11:59 -0400

On Jun 9, 2008, at 5:34 PM, Bill Burke wrote:
>>> For an EE 6 app-server, IMO, we should really figure out and
>>> define how Web Beans and EJBs *must* interact with JAX-RS in 1) a
>>> single vendor solution and 2) a thirdparty JAX-RS implementation
>>> plugged into an EE environment.
>>> In all the above cases, users are going to struggle with
>>> portability unless something is defined by the specification.
>> I agree we're going to need to do that for EE 6 but, given the
>> differing timelines, I think we're going to have to defer some of
>> those questions until after 1.0. For now I want to avoid specifying
>> anything that is going to make the integration harder when we do it.
> Ok, yeah, I see your point. We do have customers that want this
> stuff finished/finalized yesterday rather than months(years?) from
> now.
> Can we get a new spec revision released at EE 6 timeframe to fill in
> the EE integration holes?
We discussed this question in an internal EE coordination meeting
yesterday evening and we think that a maintenance release of JAX-RS
(version 1.1) is the best way to address EE 6 integration. This will
free us to concentrate on getting 1.0 done without being tied to other
still-in-development specs that are on a longer timeline.

Hopefully EE 6 integration won't require any API changes, rather it
will involve firming up the existing section 6.2 text and adding some
additional requirements around what types of component JAX-RS
annotations can be applied to.


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