wse 3.0 input / output correlation

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jon_ProactiveLogic - 03 May 2006 17:47 GMT

Hi,

I have a custom policy assertion that creates service input and output
filters. Is there a way to store information in the input filter so that it
will be available to the output filter? The output filter needs to be aware
of some of the things the input filter did in one of my scenarios. I
remember in one of the web casts that the presenter said correlation was
going to be easier in WSE 3.0. I do not want to put the information in the
SOAP message itself.

I guess I could use Thread Local Storage at the minimum. Does anyone know
the recommended way to do this?

Thanks,
Jon

Reply to this Message

Jon_ProactiveLogic - 03 May 2006 19:17 GMT

Looks like SoapContext.OperationState will do the trick!

> Hi,
>
[quoted text clipped - 11 lines]
> Thanks,
> Jon

Reply to this Message

Pablo Cibraro - 07 May 2006 02:26 GMT

Exactly, it was designed for that purpose. The SoapContext also exposes the
following properties,

MessageState : state shared only for one filter
SessionState: state shared by the client or service and the filters (Input
and output) on the same side.

Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax

> Looks like SoapContext.OperationState will do the trick!
>
[quoted text clipped - 17 lines]
>> Thanks,
>> Jon

Reply to this Message

plikwords - 10 May 2006 20:47 GMT

For custom tracing policy assertions I have used a class containing a
static hash for storing message pre and post security - works well.

>Exactly, it was designed for that purpose. The SoapContext also exposes the
>following properties,
[quoted text clipped - 28 lines]
>>> Thanks,
>>> Jon

Reply to this Message

wse 3.0 input / output correlation

Free Magazines