MHonArc v2.5.0b2 -->
ebxml-msg message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [ebxml-msg] some issues affecting header design
I meant RM-Reply as defined in the WS-Reliability 1.1 specification.
On 20-Sep-04 16:25, Jacques Durand wrote:
> Doug:
>
> Let me try to cut short on commenting on a previous unclear comment..:
> I believe we'll need an ebMS message ID in addition to the RM ID,
> even if an implementation could weasel its way out - which I am not even
> sure yet.
>
> My turn to be puzzled by your fisrt paragraph below:
> Because RM-Replies are only visible to RMPs and are correlated by these
> to reqeust(s) based on RM IDs.
> I guess by RM-Reply you mean [business] response that uses "response"
> reply pattern?
> So the use of RefToMessageId seems rather orthogonal to this - it would
> allow for correlating in ebMS
> where RM headers are no longer visible.
>
> Jacques
>
>
>
>