Re: need to execute client SoapExtension after Security

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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



"casey chesnut" <casey@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OJqJAmBUFHA.2712@xxxxxxxxxxxxxxxxxxxxxxx
> 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
>
> "Roman Kiss [MVP]" <rkiss@xxxxxxxxxxx> wrote in message
> news:ekcDn%23AUFHA.3436@xxxxxxxxxxxxxxxxxxxxxxx
>> 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
>>
>>
>>
>> "casey chesnut" <casey@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message news:Osvfxm$TFHA.544@xxxxxxxxxxxxxxxxxxxxxxx
>>> 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
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • RE: Http 400: bad request
    ... since I created the test client app and test server app at the same time, ... by the test server app. ... I am not sure if I configure the client and server policy right for the test ... you have two webservices(secured by WSE 2.0) and one ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: How does sql ExecuteReader() work?
    ... the SqlClient provider executes the query which begins a thread of execution on the server. ... At this point control returns immediately to the client which the client provider waits for a back-channel packet that says the first row of the data is available. ... The server, processes the SQL and once it finds rows that match the criteria saves the rows to a server-side buffer. ...
    (microsoft.public.data.ado)
  • WSE2 - Large DIME attachments failing
    ... I've seen several posts across the web regarding people having difficulties ... have set maxRequestLength (WSE) on both client and server to ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: No WSE Proxies
    ... This was a problem with the client and not the server. ... your comment about how the WSE proxies are created on the client for WinForm clients got me looking in the right direction. ... Based on my understanding, this is possibly occured for autogenerated web service proxy, so is your client applicationan ASP.NET web application also? ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: need to execute client SoapExtension after Security
    ... On the server side, the WSE extension is closed to the wire (priority="1", ... > i've got a WS using WSE 1.1 for security. ... > 2) client side executes my custom SoapExtension, ...
    (microsoft.public.dotnet.framework.webservices.enhancements)