OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: Request for clarification - multiple payloads


Thanks for the example. My question was based on what David Marshall listed as an OTA requirement:

<requirement>In the OTA we need to send at least two payload documents
within each ebXML message envelope.</requirement>

I thought the answer that was offered to David was, yes you can pack these two (or more) payload documents in a MIME
multipart/* structure and send it out as payload in a single ebXML message.

Now, my question was based on the possibility that the two payload documents could generate two response documents, that could again comeback as payload in a single ebXML message.  I was suggesting that "when we apply this to the case of Synchronous exchanges, this would boil down to a simple straightforward extension of the model. That is, multiple responses (if any) would come back in the payload of the synchronously delivered  response message".

I take it,  there is no issue with it.


Dick Brooks wrote:


The GISB profile of EDIINT AS2 contains an example of a multipart
acknowledgement, here is how I've envisioned the GISB
acknowledgement receipt appearing in an ebXML Acknowledgement Message using
HTTP binding:

HTTP/1.1 200 OK
Server: Group 8760 GISBAgent
Content-Length: 2739
Content-type: multipart/related; type="application/vnd.eb+xml";

Content-ID: ebxmlheader-8760-2081904539
Content-type: application/vnd.eb+xml; charset="UTF-8"

<?xml version ="1.0" encoding="UTF-8"?>
<!DOCTYPE ebXMLHeader SYSTEM "level1-10022000.dtd">
<ebXMLHeader xmlns = "http://www.ebxml.org/namespaces/ebXMLHeader"
Version = "0.21"
MessageType = "Acknowledgement">
<DocumentDescription xml:lang="en-us">
<PartyId context = "DUNS">059397184</PartyId>
<PartyId context = "DUNS">943561654</PartyId>
<RefToMessageId>Not Applicable</RefToMessageId>
<ReliableMessagingInfo DeliverySemantics ="OnceAndOnlyOnce"/>
Content-ID: 8760.com2081904536
Content-Type: multipart/report;  report-type="GISB-Acknowledgement-Receipt";

Content-type: text/html

<HTML><HEAD><TITLE>Acknowledgement Receipt Success</TITLE></HEAD> <BODY><P>
</P> </BODY></HTML>
Content-type: text/plain


Dick Brooks

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC