Re: [ebxml-msg] Groups - Using ebMS dummy headers to route WS-RM lifecycle messages.doc uploaded

[Sander Fieten <sander@fieten-it.com>]

I think this proposal differs so significantly from the V3 core spec  
that we can't say that endpoints conforming to the core spec are able  
to connect to an I-Cloud with only a change in configuration. To me  
this seems to be a big problem of this proposal.

The WS-A EPR option might also not be specified in the core spec but  
the usage of ws-rm requires an endpoint to know the EPR of the  
destination. In the point-to-point situation this is simple because  
the URL of the other endpoint is its EPR, no reference parameters are  
needed. In the multi-hop case however the URL it unknown, so  
additional information is needed to indentitfy the destination. It  
would be logical that the extra information is expressed in EPR  
parameters. So it could be reasoned that this option is within the  
core spec (although I admit it is certainly not straightfoward).

Drawback of the WS-A EPR approach is that intermediaries have to look  
in two places for addressing/routing information. In ebMS user  
messages in the ebMS messages and otherwise in the WS-A header. This  
based on the assumption that ebMS user message will not contain a WS-A  
header because this would only duplicate already available information.

Sander



On 20 mei 2008, at 23:02, pvde@sonnenglanz.net wrote:
> The document named Using ebMS dummy headers to route WS-RM lifecycle
> messages.doc has been submitted by Mr. Pim van der Eijk to the OASIS  
> ebXML
> Messaging Services TC document repository.
>
> Document Description:
> Discussion on storing routing metadata in ebMS dummy headers instead  
> of
> WS-Addressing reference parameters.
>
>
> View Document Details:
> http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/document.php?document_id=28338
>
> Download Document:
> http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/download.php/28338/Using%20ebMS%20dummy%20headers%20to%20route%20WS-RM%20lifecycle%20messages.doc
>
>
> PLEASE NOTE:  If the above links do not work for you, your email  
> application
> may be breaking the link into two pieces.  You may be able to copy  
> and paste
> the entire link address into the address field of your web browser.
>
> -OASIS Open Administration