Uploaded image for project: 'OASIS ebXML Messaging Services TC'
  1. OASIS ebXML Messaging Services TC
  2. EBXMLMSG-117

ebMS3 Part 2 section 4.4.2 and 4.5, P-Mode improvements

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: Part Two
    • Labels:
      None
    • Proposal:
      Hide

      In section 4.4.2

      Change:

      "The value for Pmode.ErrorHandling.Report.AsResponse MUST NOT be “True”"
      to
      "The value for Pmode[1][source].ErrorHandling.Report.AsResponse MUST NOT be “True”.
      (See section 4.5 for the use of the "source" label)"

      Remove:

      "The value for Pmode[1].Reliability.AtLeastOnce.ReplyPattern MUST NOT be “Response”."

      In section 4.5, add

      "Some P-Mode parameters may apply both to fragment messages and
      to the source message. If the parameter value to use is different
      for the two cases, this can be disambiguated using the label
      notation introduced in section D.2.1. of [EBMS3CORE]. To express
      that errors for the source message are reported asynchronously,
      but errors for fragment are reported synchronous, the following
      notation is used, with "fragment" applying to ebMS3 fragment
      messages and "source" to the ebMS3 source message:

      Pmode[1][fragment].ErrorHandling.Report.AsResponse: True
      Pmode[2][source].ErrorHandling.Report.AsResponse: False

       

      Show
      In section 4.4.2 Change: "The value for Pmode.ErrorHandling.Report.AsResponse MUST NOT be “True”" to "The value for Pmode [1] [source] .ErrorHandling.Report.AsResponse MUST NOT be “True”. (See section 4.5 for the use of the "source" label)" Remove: "The value for Pmode [1] .Reliability.AtLeastOnce.ReplyPattern MUST NOT be “Response”." In section 4.5, add "Some P-Mode parameters may apply both to fragment messages and to the source message. If the parameter value to use is different for the two cases, this can be disambiguated using the label notation introduced in section D.2.1. of [EBMS3CORE] . To express that errors for the source message are reported asynchronously, but errors for fragment are reported synchronous, the following notation is used, with "fragment" applying to ebMS3 fragment messages and "source" to the ebMS3 source message: Pmode [1] [fragment] .ErrorHandling.Report.AsResponse: True Pmode [2] [source] .ErrorHandling.Report.AsResponse: False  

      Description

      Some fixes for Split & Join P-Mode configuration

      First, in Section 4.4.2, it should be clarified that asynchronous error handling is
      required for the source message. There may be errors in fragments, and then there is no
      problem to report them synchronously. To be able to specify parameters for either
      fragments or source, a disambiguating notation should be added to section 4.5.

      Second (minor), there is a reference "Pmode.ErrorHandling", this should be
      "Pmode[1].ErrorHandling"

      Third, 4.4.2 states that reliability acknowledgments should be asynchronous, but if
      reliability applies to fragments, there is no problem with synchronous receipts.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              pvde Pim van der Eijk
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: