[SOLVED] SOAP <change>

[ljm]

What does a SOAP client have to do in order to be guaranteed to always get a <change> element in the SOAP response to a server update?

My understanding is that the client doesn't actually have to do anything. ie. so long as the client doesn't provide the <nosession> element it is always going to get a <change> element back. Is that right?

Just want to confirm...thanks!

[ljm]

And a second sort-of-related question.

Reading soap.txt, it's clear that the <soap:Header> element is optional. However there's no mention of when it's supplied and when it isn't.

From reading the code, it looks as if it's always supplied unless there's a soap:Fault.

I'm currently debugging a soap exchange in which the SOAP responses all look reasonable except that none of them have a soap:Header element.

I'm scratching my header re: what might be causing the soap:Header element to be missing. Any ideas?

[ljm]

Don't worry - I worked out as much of an answer to this as I needed.

My problem was that with <nosession/> in the request, 4.5.4 wasn't returning a soap:Header element in the FooReponse (where Foo is a Create/Modify). That feels like a bug to me but given that that 4.x is deprecated I won't bother filing a bug report. In any case, without the <nosession/> element, it works as one would expect.