MSH behaviour if TO/FROM is not recognised

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor
    • Component/s: Core Spec
    • None
    • Hide

      Provide details on EBMS error codes that should be used if such a condition occurs. Alternately provide a clarification that this condition could be handled by the business layer - this assumes that the TO/FROM metadata would need to be passed to the business layer in something other than the actual message contained in the soap body or attachment.

      Show
      Provide details on EBMS error codes that should be used if such a condition occurs. Alternately provide a clarification that this condition could be handled by the business layer - this assumes that the TO/FROM metadata would need to be passed to the business layer in something other than the actual message contained in the soap body or attachment.

      Section 5.2.2.2. eb:Messaging/eb:UserMessage/eb:PartyInfo states that TO/FROM are required yet there is no subsequent detail on the behaviour of the MSH if these are not recognised on a receiving MSH.

      Thanks to Michael Leditschke for raising this

            Assignee:
            Unassigned
            Reporter:
            Theo Kramer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: