Re: [messaging-dev] Clarification on Jakarta Messaging 3.1 Shared Subscr

[Jean-Louis Monteiro <jlmonteiro@xxxxxxxxxxxxx>]

Hi Patrick,

They are tested in the API Signatures Tests, and the API/Javadoc is considered part of the spec. I'd still agree that we should add it to the spec document itself to get rid of the ambiguity.

So to me, it's required to be compatible.

I don't think we have coverage for it in the TCK. So another improvement to do.

Hope it helps

--

Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

On Thu, Dec 19, 2024 at 10:48 PM Patrick Deasy via messaging-dev <messaging-dev@xxxxxxxxxxx> wrote:

Hello,

I seek clarification on Jakarta Messaging 3.1 and JMS 2.0 specification in relation to shared subscriptions(ref 8.3.2 and 8.3.4).

It outlines the addition of createSharedDurableConsumer and createSharedConsumer on JMSContext and Session. These need to be implemented to be Jakarta Messaging 3.1 compliant.

Connection also has createSharedConnectionConsumer and createSharedDurableConnectionConsumer methods added. Do those connection methods need to be implemented in order to be Jakarta Messaging 3.1 compliant? They are not mentioned in the spec(ref 8.3.2 and 8.3.4).

Kind regards,

Patrick

_______________________________________________
messaging-dev mailing list
messaging-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org