jms-spec
  1. jms-spec
  2. JMS_SPEC-25

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

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 1.1
    • Fix Version/s: None
    • Labels:
      None

      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.

        Activity

        Hide
        John D. Ament added a comment -

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

        Show
        John D. Ament added a comment - If we setup CDI integration, +1 maybe to standardize on the CDI extension approach?
        Hide
        Nigel Deakin added a comment - - edited

        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.

        Show
        Nigel Deakin added a comment - - edited 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.
        Hide
        Nigel Deakin added a comment - - edited

        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.

        Show
        Nigel Deakin added a comment - - edited 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.
        Hide
        Nigel Deakin added a comment -

        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.

        Show
        Nigel Deakin added a comment - 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.

          People

          • Assignee:
            Nigel Deakin
            Reporter:
            Nigel Deakin
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: