3 Replies Latest reply on Jun 29, 2006 2:25 AM by docampbell

    Does JBoss provides WS-Reliable Messaging out-of-the-box?

    m3poulin

      Do we need to use such things as Axis 2- Sandesha2 to be able to work with WS-Reliable Messaging on JBoss, or such feature is available from JBost first hand?

      Thanks,
      - Michael Poulin

        • 1. Re: Does JBoss provides WS-Reliable Messaging out-of-the-box
          burrsutter

          JBoss does not have a WS-RM implementation out of the box today.

          However, you can push SOAP messages around via JMS assuming you don't need to interoperate with anything other than a Java client (VB doesn't speak JMS).

          http://labs.jboss.com/portal/jbossws/user-guide/en/html/jms-transport.html

          Burr

          • 2. Re: Does JBoss provides WS-Reliable Messaging out-of-the-box
            marklittle

            Plus it's on the roadmap and we are active participants in the OASIS WS-RX technical committee.

            • 3. Re: Does JBoss provides WS-Reliable Messaging out-of-the-box
              docampbell

              Hi Burr,

              I have a post (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=85626) on this forum related to Reliable Messaging. I have implemented a version which is going to go open source (for comments really) that you may be interested in. If I can get the problem sorted I will be posting the code and documentation to open source within the next month.

              It provides WS-Reliable Messaging "at-least-once" delivery and is (will be!!) based on JBoss as the WS container, with a persistence mechanism based on MySQL and uses open source Quartz scheduler to perform background tasks.

              It started off based on WebLogic (for WS and persistence), but we have modified (are still in the process of) it to enable us to open source it. Not sure if it will help, but it's going out there to be "shot at" !! We have done some testing with .Net, but interoperation with that is proving difficult - we have managed to get sequences exchanged and messages sent, but are currently working on a problem with acknowledgements. .Net sends an empty additional SOAP message with no body to indicate the last message, rather than tagging the last message indicator to the real last message and we have problems with the empty SOAP body (well, Axis does and WebLogic does, but have yet to see if JBoss does!)

              Will add a post here when it is released if that would be of interest to you.

              Cheers,

              Dominic.