Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-76

Vote for WS-Reliable Messaging

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Obsolete
    • Major
    • jbossws-voting
    • None
    • productization
    • None

    Description

      Please vote for WS-ReliableMessaging if this is relevant to your enterprise web services

      http://www-106.ibm.com/developerworks/library/ws-rm/

      This specification (WS-ReliableMessaging) describes a protocol that allows messages to be delivered reliably between distributed applications in the presence of software component, system, or network failures. The updates are based upon the suggestions collected from the WS-ReliableMessaging Feedback Workshop held in July 2003 and the Interoperability Workshop help in October 2003. The protocol is described in this specification in an independent manner allowing it to be implemented using different network transport technologies. To support interoperable Web services, a SOAP binding is defined within this specification.

      The protocol defined in this specification depends upon other Web services specifications for the identification of service endpoint addresses and policies. How these are identified and retrieved are detailed within those specifications and are out of scope for this document.

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. JBWS-529 Interoperability: Test WS-ReliableMessaging Endpoints

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Task - Represents a small unit of work that is not end-user facing. JBWS-515 Provide an initial implementation for WS-ReliableMessaging

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. JBWS-2048 Rewrite initial RM implementation to ensure HA and QoS

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              tdiesler@redhat.com Thomas Diesler
              Votes:
              15 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: