Thanks Simon, This is very helpful. I will go through the link and compare the notes with you.
> -----Original Message----- > From: Simon Laws [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 27, 2007 2:21 PM > To: [email protected] > Subject: Re: Passing context from ws binding to a component implementation > > On 9/27/07, Dinesh Shahane <[EMAIL PROTECTED]> wrote: > > > > Hi Simon, > > > > As you pointed, the context information could be (should be) processed > > using > > policy intents but I couldn't find the API to implement the runtime for > > such > > intents. > > > > Is there any way to extend the web services binding to process custom > > policies? Any pointers will be appreciated. > > > > Thanks, > > Dinesh > > > > > > > > -----Original Message----- > > From: Simon Laws [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, September 25, 2007 9:43 AM > > To: [email protected] > > Subject: Re: Passing context from ws binding to a component > implementation > > > > On 9/25/07, Dinesh Shahane < [EMAIL PROTECTED]> wrote: > > > > > > I want to process transport headers and custom soap headers in my > > > component, > > > what is the best way to propagate this information? The soap headers > > are > > > not part of the abstract operation signature and I cannot alter the > wsdl > > > > > contract. The component could be exposed using multiple bindings and > > each > > > binding could optionally provide the context information using > transport > > > or > > > soap headers. Is there any easy way to achieve this? > > > > > > > > > > > > Thanks in advance, > > > > > > > > > > > > Dinesh > > > > > > > > > > > > > > > > > > Hi Dinesh, > > > > I'm sure there was a conversation about this previously one the list. Of > > course I can't put my finger on it and I don't remember the detail. It > > sounds like what you are asking for is some API to provide access to > > context > > that is passed in the message that is not part of the actual body. > > > > There is a danger with this kind of thing in that the service begins to > > depend on information that is not described as part of the service > > contract > > and which is subject to local policy. > > > > Is the information processing you describe something that should be > > handled > > by policy intents that could be applied to the bindings you use (or even > a > > new binding) ? > > > > Regards > > > > Simon > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > Hi Dinesh, > > Yes I need to learn more about how the policy implementation works in > Tuscany too. Venkat has done the implementation work so far. I also > noticed > that Ant gave some advice on what to look at first here ( > http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg24210.html) so > I'm going to look at that tomorrow. We can compare notes ;-) > > Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
