jsr343-experts@jms-spec.java.net

[jsr343-experts] Re: JMS Support for DI

From: Nigel Deakin <nigel.deakin_at_oracle.com>
Date: Tue, 25 Oct 2011 18:52:21 +0100

On 25/10/2011 18:13, Clebert Suconic wrote:
> If we didn't have to be backward compatible, I would suggest we just always keep Consumers and Producers only while
> simplifying the API.
>
> For Request-Response, we could have createconsumer and createProducer on the super class for this new Producer and
> Consumer, so objects created manually outside of this new annotation would be part of the same annotation. Something
> like that.. I'm not sure
>
> If we need to keep compatibility, We could just follow the new interface as you suggest.. however I'm not sure I like
> the idea.
>
> Are we set on these rules for compatibility?
>
> Can't we just extend the model like EJB 1.1 <-> EJB 2 did? we keep the old stuff while creating a new package for new
> applications?

Yes, "keeping the old stuff whilst creating a new package for new applications" is certainly something we can do. This
is fine in terms of compatibility. The kind of change you're speculating about would require new interfaces anyway.

So it's fine to continue brainstorming...

Nigel