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
