i've got a WS using WSE 1.1 for security.
the scenario i need to happen is as follows:
1) client side executes WSE security
2) client side executes my custom SoapExtension, and sends request
3) server side executes my custom SoapExtension
4) server side executes WSE security
the problem i'm having now is getting my custom SoapExtension to execute
after WSE.
i am declaring it as an Attribute on the proxy with a priority of 2,
but it is still getting executed before Security.
so how do i get it to execute after WSE?
after i get past this, the next problem will be how to get it to execute
before WSE on the server side.
Thanks,
casey
http://www.brains-N-brawn.com
Hi Casey,
On the server side, the WSE extension is closed to the wire (priority="1",
group="0"). You can inject your custom extension based on the priority and
group attributes only in the config file. Note that the attributed method
can not change a group value, it is always group="1" (the lowest one).
server side example:
<soapExtensionTypes>
<add type="YourExtensionClass, ...." priority="1" group="0" />
<add type="Microsoft.WebServicesExtension, ..." priority="2" group="0" />
</soapExtensionTypes>
HTH
Roman
> i've got a WS using WSE 1.1 for security.
> the scenario i need to happen is as follows:
[quoted text clipped - 16 lines]
> casey
> http://www.brains-N-brawn.com
casey chesnut - 03 May 2005 20:51 GMT
Thanks Roman,
on the client side, all i've come up with is to use my WSE implementation,
so that i can run the custom extension after the request and before the
response.
casey
> Hi Casey,
>
[quoted text clipped - 36 lines]
>> casey
>> http://www.brains-N-brawn.com
Roman Kiss [MVP] - 03 May 2005 21:13 GMT
That's correct. The client side has to be handled in your extension state. I
made the same for my DimeBridge [1]. The other choice (I didn't try it) is
to reorder groups programatically.
Roman
[1]
http://www.codeproject.com/cs/webservices/DIMEBridge.asp
> Thanks Roman,
>
[quoted text clipped - 45 lines]
>>> casey
>>> http://www.brains-N-brawn.com