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


Help: OASIS Mailing Lists Help | MarkMail Help

wsrm message

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

Subject: ws processing layers with successive wsdl descriptions

Lets look at a typical 2005 scenario.

There is a user wsdl for operation foo with one message part fooInput, 
which is specified as an operation input message, and another message
Part fooOutput specified as the operation output message.

The producer invokes the wsdl operation with fooInput on the sending 
RMP. Now this “user” level wsdl is protected by wsrm features,
thus the sending RMP adds the wsrm:request element to the soap header
on the input message, and it is stripped by the receiving rmp before 
delivering the fooInput part to the producer.

The consumer does a respond invoke on the receiving rmp with the 
fooOutput element, and the receving RMP adds the wsrm:response
element to the soap header of the response The sending RMP receives the 
aggregate output message, and strips off the wsrm:response, and returns 
the fooOutput part to the producer.

Now lets put ws security into the picture.

The ws security processor adds the ws security element to the header of 
the request, and the receiving ws security processor strips
Off the ws security header and delivers the fooInput and the 
wsrm:request header element to the receiving rmp.

On response, the ws security processor adds a ws security header element 
to the receiving RMP provided wsrm:Response plus fooOutput element. The 
sending ws security processor strips off the ws security response 
header, to give the sending rmp the wsrm:response with the fooOutput 

This could all be described with “effective” wsdl descriptions for each 
“level”/”Order” of the ws header processing

The ws reliability wsdl would have fooRel as the operation with input 
message parts fooInput plus wsrm:Request, and with output message
parts fooOutput plus wsrm:response.

The ws security “level” wsdl would have fooSec as the operation with 
input message parts fooInput, wsrm:request, and wss:requestHeader, and
output message parts fooOutput plus wsrm:response plus wss:respnseHeader 

I just want to point out that we could describe the boundaries of wss 
processing )i.e. succesive layers)
each having their own effective abstract. wsdl spec.

This might help to explain what is going on, even if the “effective” 
WSDL is never actually formally registered. It is useful for 
conceptually explaining what is going on.

Tom Rutt	email: tom@coastin.com; trutt@us.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133

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