[JMS_SPEC-25] Standardise the interface between a JMS provider and a Java EE application server Created: 06/Jul/11  Updated: 07/Feb/13

Status: Open
Project: jms-spec
Component/s: None
Affects Version/s: 1.1
Fix Version/s: None

Type: Improvement Priority: Critical
Reporter: Nigel Deakin Assignee: Nigel Deakin
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: jms21-forreview-major

 Description   

We need to standardise the interface between a JMS provider and a Java EE application server, to allow portability of JMS providers between application servers.

The frontrunner here is to mandate the provision of a JCA resource adapter, though an alternative may be to extend and make mandatory the existing Chapter 8 API.



 Comments   
Comment by John D. Ament [ 06/Jul/11 ]

If we setup CDI integration, +1 maybe to standardize on the CDI extension approach?

Comment by Nigel Deakin [ 21/Jul/11 ]

Following discussions in the expert group mailing list the expert group has agreed in principle to make it mandatory for a JMS vendor to provide a JCA resource adapter to allow their JMS client to be used from any Java EE application server.

Comment by Nigel Deakin [ 07/Feb/13 ]

Following a further discussion , the JSR 343 expert group has changed its view and decided that it should not be mandatory for a JMS vendor to provide a JCA resource adapter.

Comment by Nigel Deakin [ 07/Feb/13 ]

Given that the EG has rejected making it mandatory to provide a resource adapter, should it be mandatory to implement some other API for application server integration, such the optional chapter "JMS application server facilities" in the JMS 2.0 spec? Or is it OK for vendors to continue to develop JMS implementations that can't used in a Java EE application?

Tagging for further review in JMS 2.1.

Generated at Fri Jan 20 13:21:18 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.