RE: [wsrm-comment] out of curiosity

With ebMS 2.0 it is exactely as you describe. They discussed changing it
to individual elements without a container for ebMS 3.0. I can't find
the link anymore but it was in their mailinglist/ meeting minutes.

It has something to do with the way soap1.2 is extendible as far as I
can remember.

Ronald

> -----Oorspronkelijk bericht-----
> Van: John Fuller [mailto:]
> Verzonden: donderdag 26 juni 2003 0:58
> Aan: 
> Onderwerp: [wsrm-comment] out of curiosity
> 
> 
> right now we have a specification for elements for requests and 
> responses,
> would it simplify things to have a named RM:RequestHeader 
> element/header
> contain (MessageHeader, ReliableMessage, MessageOrder)
> and a named RM:ResponseHeader  contain (MessageHeader, RMResponse)
> rather than treating the elements as individual headers in the
> SOAP header?
> 
> This would let a service build the right kind of object right away 
> instead
> of wading in past the message header.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: 
> For additional commands, e-mail: 
> 
>