Priority and Group settings in SOAPExtensions.
- From: "John Jenkins" <john_Jenkins@xxxxxxxxx>
- Date: Sat, 02 Apr 2005 18:16:04 GMT
My second attempt at the same question...
Can someone clarify the precedence of execution for SOAPExtensions?? I have
a security extension which I configure in Web.Config. Works great thanks for
that.
I have another extension which I only want to apply to a couple of web
methods, so I create a SOAPExtensionAttribute so I can decorate the
appropriate web method.
I want the >>second<< extension to execute first (because I need access to
security info from the SOAP messagefor the extension to work.) so I set its
priority to "0". Remember this is the one configured by decorating the
apropriate web methods.
I then set the Group on my security extension (configured in web.config) to
"1" and priority="1".
To me this would imply my >>second<< extension should execute first.
It appears to >>try<< to execute first but there is >>NOTHING<< in the
message stream. I know it executes first because I log details.
OK, so I change the second extension to be configured via web.config,
setting group to "0" and priority="0". This works fine!
Can someone tell me what is going on. I cannot find anything on MSDN to help
me out here.
As always any help greatly appreciated.
.
- Follow-Ups:
- Re: Priority and Group settings in SOAPExtensions.
- From: Dilip Krishnan
- Re: Priority and Group settings in SOAPExtensions.
- Prev by Date: RE: autoIssueSecurityContextToken SoapActor
- Next by Date: Re: message encryption
- Previous by thread: RE: autoIssueSecurityContextToken SoapActor
- Next by thread: Re: Priority and Group settings in SOAPExtensions.
- Index(es):
Relevant Pages
|