savas parastatidis

Adding to Aaron’s WSE wish list

Aaron Skonnard posted his WSE 3.0 wish list. I meant to add to his list more than a week ago but didn’t get the chance.

I will agree with Aaron’s and other people’s requests and I would like to add one of my own…

Currently, if you change the addressing information of a SoapEnvelope while in the filter pipeline, that addressing information is not used to create the transport channel. Ok, granted. You may want to include WS-Addressing headers in the envelope that do not reflect the transport actually used for the transfer but we should at least have a way to change the transport addressing stuff from within the filter pipeline. Perhaps a TransportContext.Current.Addressing class or something similar? Perhaps this is already supported and I have missed it. I wonder how/if this is done in Indigo.

Otherwise, the more WS-* protocols supported, the better.

2 responses to “Adding to Aaron’s WSE wish list”

  1. Steve Maine
    Check out the EndpointReference.TransportAddress property. I don’t recall off the top of my head if you can set this directly, but in either case setting EndpointReference.Via works too.
  2. Savas Parastatidis
    Hey Steve, thanks for this. I know of the Via property. The problem is that changing it through SoapContext.Current.Addressing when the filtering pipeline has started doesn’t have an effect. This is because the SoapSender class sets the TransportChannel before calling the pipeline.