Missing SOAP header in ECP response

[Cantor, Scott]

On 12/13/12 12:11 AM, "Brent Putman" <putmanb at georgetown.edu> wrote:
>
>It's true that in v3, the encoders/decoders and message handling in
>general is completely different.  But I think the server-side SOAP
>decoder/encoder stuff that's in v2 openws works ok, and I know that is
>what we used in the delegation work, so it is at least somewhat tested.
>I wouldn't really call it in flux at this point.  Although maybe you are
>referring to something else.

I didn't think the client side stuff was tested much at all, but more the
point is the V3 thing. I didn't think it would be worth spending a lot of
time making the V2 API work when it's different going forward.

In terms of client code, the abstractions around message handling are
really not as valuable as on the server side where the profile code has to
deal with multiple formats. An ECP client is just doing the SOAP.

-- Scott