Uploaded image for project: 'Spring Framework'
  1. Spring Framework
  2. SPR-17583

Clarify whether spring-jms 5.x is still able to run with a JMS 1.1 provider

    Details

    • Last commented by a User:
      true

      Description

      Starting with 5.0.0, the dependency to the JMS API was changed in spring-jms for 2.0.

      Spring documentation and/or javadocs might make clear that this does not mean that spring-jms 5.x actually requires the provider used to implement 2.0.

      In my case, I am evaluating the impacts to upgrade some applications I have from spring 4.x to 5.x. For other external dependencies/impacts like for instance JEE APIs like servlet-api or JPA, Spring documentation make this clearer. For instance, LocalContainerEntityManagerFactoryBean's javadoc make it clear that JPA 2.1 is required. As I currently depends on a JMS provider (Oracle AQ) that only implements JMS 1.1, to be sure I would not have issues I had to download spring-jms code and search in it for calls to ConnectionFactory.createContext. Only after doing that I was able to see that there is no such call, and was able to conclude (yet without 100% certainty) that the upgrade of the dependency to 2.0 must have been to allow the spring-jms ConnectionFactory decorators to be 2.0 compliant.

      Spring Framework Reference documentation and/or some javadoc (maybe the one of @EnableJms) might make this clear.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                juergen.hoeller Juergen Hoeller
                Reporter:
                jgslima João Guilherme de Souza Lima
                Last updater:
                Spring Issuemaster
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  47 weeks ago