Hi, I'd be interested in learning more about SOAP actors myself.
The way I currently understand actors is that SOAP messages are bounced from one actor to another, and each actor processes the SOAP message in some way. I haven't seen any implementations, myself, although I'm sure there are some. Microsoft has come up with a SOAP routing protocol, SOAP-RP, (http://www.gotdotnet.com/team/xml_wsspecs/soap-rp/default.html) that appears to define how intermediaries are specified on the message path, for one-way messages. I hope this helps - I just started reading this specification yesterday. Unfortunately, a search on google for "SOAP actors" tends to turn up daytime television web pages ;) - It is sort of unfortunate terminology. Thanks, Jeff ----- Original Message ----- From: "Martin Leboeuf" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, October 29, 2001 8:23 AM Subject: SOAP actor attribute > Hi ! > > I have searched far and wide, and found very little documentation about SOAP > other then the W3C Specs or very similar doc. I am looking for something > like a developer's/programmer's guide. > > For my specific question : I have a hard time fully understanding the > meaning/utility/implications of the SOAP actor attribute of the SOAP header. > E.g. does the actor attribute apply to SOAP RPC services or is it for > one-way messages only ? How does one specify intermediairies along the > message path ? For what purposes can actors be used/ not be used ? Any SOAP > implementations implementing the actor attribute, b.t.w. (Apache SOAP 2.2 > seems not to) ? > > Any pointers very much appreciated, especially code examples ! > > As you see, I am not an expert with SOAP. We have been using servlet-based > technology up until now, and plan on using web services in the (as near as > possible) future. > > Thanks, > > M. > >
