RE: [ws-caf] Context query

["Tony Fletcher" <tony_fletcher@btopenworld.com>]

Dear Kevin,

The version of the (WS-Context) schema that I have as the current one
(27/04/2005) still has the element 'context' defined.  I wonder if you are
looking at a later version?  Could you please mail me, or point me to the
latest versions of the spec, schema and WSDL for WS-Context.  Thank you.

By the way, thank you for your previous mail to me it was / is helpful and I
still intend to reply to it sometime - sorry for the ongoing delay.

Best Regards     Tony
A M Fletcher
Tel: +44 (0) 1473 729537   Mobile: +44 (0) 7801 948219
 tony.fletcher@choreology.com    amfletcher@iee.org       (also
tony_fletcher@btopenworld.com)
 


-----Original Message-----
From: Kevin Conner [mailto:Kevin.Conner@arjuna.com] 
Sent: 06 June 2005 09:52
To: WS-CAF
Subject: [ws-caf] 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.