Standardise the interface between a JMS provider and a Java EE application server

[glassfishrobot]

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.

Affected Versions

[1.1]

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/jms-spec/issues/25
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @nigeldeakin

[glassfishrobot]

@glassfishrobot Commented Reported by @nigeldeakin

[glassfishrobot]

@glassfishrobot Commented genomeprjct said: If we setup CDI integration, +1 maybe to standardize on the CDI extension approach?

[glassfishrobot]

@glassfishrobot Commented @nigeldeakin said: 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.

[glassfishrobot]

@glassfishrobot Commented @nigeldeakin said: 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.

[glassfishrobot]

@glassfishrobot Commented @nigeldeakin said: 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.

[glassfishrobot]

@glassfishrobot Commented This issue was imported from java.net JIRA JMS_SPEC-25