Receipt format for reception awareness

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: Core Spec
    • None
    • Hide

      The use of UserMessage elements for reception awareness was discussed at length, my proposal would be to not reopen the format discussiong but instead relax the schema to allow the use by dropping the requirement that content of receipt be from another namespace.

      <xsd:complexType name="Receipt">
      <xsd:sequence>
      <xsd:any processContents="lax" maxOccurs="unbounded"/>
      </xsd:sequence>
      </xsd:complexType>

      Show
      The use of UserMessage elements for reception awareness was discussed at length, my proposal would be to not reopen the format discussiong but instead relax the schema to allow the use by dropping the requirement that content of receipt be from another namespace. <xsd:complexType name="Receipt"> <xsd:sequence> <xsd:any processContents="lax" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType>

      AS4 uses copies of UserMessage elements in receipt for non-repudation awareness. This satifies the requirement that the content of Receipt is a non-empty sequence, but the UserMessage element is from the same ebMS namespace as the Receipt, whereas the schema requires it to be from another namespace. We missed this when we changed the format for reception awareness receipts.

      <xsd:complexType name="Receipt">
      <xsd:sequence>
      <xsd:any namespace="##other" processContents="lax" maxOccurs="unbounded"/>
      </xsd:sequence>
      </xsd:complexType>

            Assignee:
            Unassigned
            Reporter:
            Pim van der Eijk (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: