2 Replies Latest reply on Jul 10, 2009 2:51 AM by Tim Fox

    JBM compatibility across releases

    dave s Newbie

      I can't seem to find this spelled out anywhere, so was hoping someone here could answer this. What level of compatibility can I expect (if any) across minor releases of JBoss messaging?

      For example, if I have two JBM clients, one running 1.4.0.SP3 and another at 1.4.3, could they both read and write each others' messages if the JBM server hosting the queue is at 1.4.0SP3? Any difference if it's 1.4.3? Would the answer be different if JBM 2.0 is involved?


        • 1. Re: JBM compatibility across releases
          Yong Hao Gao Master

          For jbm 1.4, you need to read the release notes for the changes. Each minor release has some bug fixes, and they all back compatible with existing functionalities, by which it means you don't need to change your application code as long as you are using public APIs.

          You shouldn't use mixed version of JBM in runtime, as some of the libs need to be consistent, for example the jboss remoting jar.

          • 2. Re: JBM compatibility across releases
            Tim Fox Master

            To clarify Howard's answer:

            For JBM 1.4 we try and keep releases compatible but we make no guarantees - sometimes we have to fix bugs or other components need to fix bugs (e.g. JBoss Remoting) which requires incompatible fixes.

            For EAP CP releases, the rules are stricter and we are required to maintain compatibility between them unless there is a critical bug whose fix requires compatibility is broken.

            JBM 2.0 is *very different* to JBM 1.4. There is no compatibility between 1.4 and 2.0