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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-caf message

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


Subject: Context query


I have a query about a change that was made to the context specification, it came to me last week while I was on holiday (sad I know).

I had assumed that one of the original intentions behind context was that the context could be passed around without intermediates having any knowledge of the contents (by intermediates in this case I mean applications, not routing).  If this is the case then I believe it is no longer true.

A recent change to context removed the wsctx:context element in favour of a derived type and element, specified in a referencing specification. This came about in response to a discussion held earlier regarding soap:mustUnderstand and context types.  One major effect of this change is that it is no longer possible to identify a context element, and therefore propagate it opaquely, unless the referencing specification is known to the intermediate application.

Should it be possible to propagate a context opaquely?

Thanks,
	Kev

-- 
Kevin Conner
Arjuna Technologies Ltd.


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