W3C home > Mailing lists > Public > public-ws-addressing@w3.org > March 2005

Can ReferenceParameters contain message addressing properties defined in WS-Addresing core

From: Anish Karmarkar <Anish.Karmarkar@oracle.com>
Date: Tue, 01 Mar 2005 13:23:02 -0800
Message-ID: <4224DD36.8070300@oracle.com>
To: "public-ws-addressing@w3.org" <public-ws-addressing@w3.org>

I know we had a discussion around this, but do not remember the resolution.

The current schema at [1] uses "##any" as the namespace restriction for 
Ref param :

   <xs:complexType name='ReferenceParametersType' >
	<xs:sequence>
	  <xs:any namespace='##any' processContents='lax' minOccurs='0' 
maxOccurs='unbounded' />
	</xs:sequence>
   	<xs:anyAttribute namespace="##other" processContents="lax"/>

   </xs:complexType>

So what happens if there is an EPR with Ref param that contains wsa:To, 
wsa:Action and wsa:ReplyTo? If I were to follow the rules in WS-A 
core/soap-binding, there will be two wsa:To soap headers and two 
wsa:Action soap headers and possibly two wsa:ReplyTo. The cardinality of 
wsa:To, wsa:Action is (1, 1) and for wsa:ReplyTo is (0, 1).

Is such an EPR conformant to WS-Addressing?

-Anish
--

[1] http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr.xsd
Received on Tuesday, 1 March 2005 21:23:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:04 GMT