[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ebxml-msg] Pull'ing a specific document
Hello
Makesh,
We
heard this requirement previously from German government
users.
There
is a feature called sub-channels (see section 2.5.4 of the Part 2) that almost
does this. If the response message is expected on the MPC
then a
server could offer sub-channels like:
or
with an XPath expression that matches SOAP headers. Right now such a convention
(to use URL query syntax) is not standardized. But it might be the easiest
way to handle this. The
eb3:PullRequest has an open content model, so we could also invent some element
syntax like
<eb3:PullRequest mpc="http://receiver.example.com/mpc123">
<eb3:RefToMessageId>messageid@sender.example.com</eb3:RefToMessageId>
</eb3:PullRequest>
But
this is a really an extension and again, is not standardized right
now.
Pim From: Makesh Rao (marao) [mailto:marao@cisco.com] Sent: 29 March 2010 23:20 To: ebxml-msg@lists.oasis-open.org Subject: [ebxml-msg] Pull'ing a specific document Hi In
initial conversations with partners/customers over AS4, I have repeatedly heard
the request to be able to Pull a particular document. The unique identifier
could be based on the UserMessage that has been exchanged earlier e.g. PO # if a
PO Message has been sent earlier. Is
there provision in the current spec to be able to support that ? My
understanding is that it is a generic Pull where the next available
document is sent in the response. Any
advice please ? Thanks Makesh |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]