Re: [soapbuilders] WASP C++ 4.0 interop endpoints
Looks good, the endpoint table on the Round 2 interop page has been updated.
Test results using the White Mesa client:
"base" -- all pass.
"Group B" -- all pass.
"Group C" -- the eight cases in which a header is expected in the response
failed because although the header entry is present, it is not within the
scope of a "encodingStyle" declaration with value
"http://schemas.xmlsoap.org/soap/encoding/" per the Group C test spec .
At runtime the client is guided by the wsdl  where the soap:header
elements have use="encoded" and
It is for this same reason that the White Mesa server doesn't handle headers
targeted at it by the WASP C++ test client, resulting in test failures .
> I would like to announce updated interop endpoints for WASP Server forC++
> base  group B  and group C , client results are at  (not
> changed), Systinet interop corner is at 
> Any feedback is highly appreciated
>  http://soap.systinet.net:6070/InteropService/
>  http://soap.systinet.net:6070/InteropBService/
>  http://soap.systinet.net:6070/InteropCService/
>  http://soap.systinet.net/waspc/interop/
>  http://soap.systinet.net/interop/
> (URL points both to wsdl file and endpoint)
> Tomas Bahnik
> Systinet Corp