
Signature
This posting is provided "AS IS", with no warranties, and confers no rights.
> You can have these, but they cannot be closest to the wire and they
> cannot change the content-type of the message. If your SoapExtension
[quoted text clipped - 5 lines]
> the wire content, we're looking to solve this in the next release. If
> your extension doesn't do compression, can you tell me what you use it for?
Yep - pipeline filters seem to be no good for me becuase I can't get
at the raw HTTP transported message, only the SOAP part. I'm wanting
to modify the message prior/after transport at the client end to allow
encryption, compression, wire level logging etc. If a client defined
SoapExtension can't get in 'before' WSE2, then I guess the only option
is to extend the WSE2 soap client proxy class and override some of its
methods - is this approach possible? What would I have to do?
Also, AFAICT whereas on the server end you can specify a SoapExtension
either via an SoapExtensionAttribute on the XML web service method
itself, or via an entry in the web.config, on the client end only the
attribute approach can be used - which has the limitation that the
SoapExtension will always be in priority group 1 (as all attribute
extensions are), whereas a config-defined extension can get 'closer to
the wire' in group 0. I wondered if I could get a client
SoapExtension in priority group 0 whether I'd be able to get to the
response meeage before WSE2 in the call chain.
Regards
Robin Meehan
Hervey Wilson [MSFT] - 03 Oct 2004 19:10 GMT
>>You can have these, but they cannot be closest to the wire and they
>>cannot change the content-type of the message. If your SoapExtension
[quoted text clipped - 13 lines]
> is to extend the WSE2 soap client proxy class and override some of its
> methods - is this approach possible? What would I have to do?
WSE is designed to do signing and encryption of the message, can you
tell us why you are doing this in your soap extension? If you are not
using WSE features, then there is no reason to activate the product for
your web services.
> Also, AFAICT whereas on the server end you can specify a SoapExtension
> either via an SoapExtensionAttribute on the XML web service method
[quoted text clipped - 5 lines]
> SoapExtension in priority group 0 whether I'd be able to get to the
> response meeage before WSE2 in the call chain.
Generally no, the implementation in WSE2 means that it is controlling
the wire. You can reconfigure WSE2 SP1 to replace the component in the
product that reads/writes from the wire - the ISoapFormatter
implementation. You might configure your own SoapFormatter into the HTTP
transport and then override the serialization / deserialization of the
message. This still doesn't give you direct access to the HTTP level stream.

Signature
This posting is provided "AS IS", with no warranties, and confers no rights.