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: Questions on WS-CAF


Dear all,

The message bellow is from one of our students here in Newcastle who is
experimenting with WS-Context. Since he can't subscribe to the mailing
list, I am forwarding his questions to the list.

Regards,
--
Savas Parastatidis
http://savas.parastatidis.name (now blogging)
 
> 
> I'm currently working on an implementation of WS-CTX as part of a
final
> year
> computing science project at the University of Newcastle. I would be
very
> grateful if the mailing list could help me clarify a few points that
I'm
> having difficulty with.
> 
> 1) If the context is changed via the setContents operation of the
Context
> Manager Port and the identifying URI is changed, how should the reply
> message
> be formatted? Should this be relying on the correlation-id to
associate
> the
> reply with the request, or should the original context URI be sent in
the
> SOAP
> header to indicate that it is part of the same operation?
> 
> 2) For all operations with the context service itself, should replies
rely
> solely on the correlation id to associate a reply with a response, or
> should
> they use a combination of this and the context identifier?
> 
> 3) What should the sender address be set to in replies? i.e. should
this
> point
> to the address that was called, or expanded to give details of the
> operation
> that is actually being called etc?
> 
> 4) for the details in the Fault types that are returned, are there any
> restrictions on what should be placed within the originator and error
code
> elements or is this entirely implementation specific?
> 
> Thank you for your help
> 
> Andrew Maule
> 




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