[PATCH 3/5] wsdapi: Register default namespaces when creating publisher.

[Owen Rudge]

Signed-off-by: Owen Rudge 
---
  dlls/wsdapi/discovery.c       | 20 +++++++++++++++++---
  dlls/wsdapi/soap.c            | 13 +++++++++++++
  dlls/wsdapi/wsdapi_internal.h |  2 ++
  3 files changed, 32 insertions(+), 3 deletions(-)

[Huw Davies]

On Mon, Apr 09, 2018 at 10:43:48PM +0100, Owen Rudge wrote:
> Signed-off-by: Owen Rudge
>
> dlls/wsdapi/discovery.c       | 20 +++++++++++++++++---
>  dlls/wsdapi/soap.c            | 13 +++++++++++++
>  dlls/wsdapi/wsdapi_internal.h |  2 ++
>  3 files changed, 32 insertions(+), 3 deletions(-)

This is consistently giving me test failures.  They are fixed after
applying [4/5], so I suspect it's a patch ordering issue.

../../../tools/runtest -q -P wine -T ../../.. -M wsdapi.dll -p wsdapi_test.exe.so discovery && touch discovery.ok
discovery.c:599: Test failed: Publish failed: 80070057
discovery.c:612: Test failed: No messages received
discovery.c:645: Test failed: Hello message not received
discovery.c:647: Test failed: AppSequence not received
discovery.c:650: Test failed: Custom header not received
discovery.c:651: Test failed: Wine namespace not received

[Owen Rudge]

> This is consistently giving me test failures.  They are fixed after
> applying [4/5], so I suspect it's a patch ordering issue.

That's odd, I'm not able to reproduce that at all. There's nothing in the third patch that should cause any difference to the output, and the changes are quite straightforward. It looks like the Publish method is returning E_INVALIDARG in your case. Could you perhaps re-run the discovery tests with WINEDEBUG=+wsdapi set and send me the log?

Thanks,

Owen