MS->Sun interop using MEX:WS-Metadata Exchange Error

Setup:
Glassfish v2b38, WSIT build 1864

Attachments:
1)service war : WsSecurity10.war
2)client side command log
3)server side log snippet

Description:
MS to Sun Interop using MEX fails.

Invoked the MS HostedClient service to run the MS clients against a Sun
service,the 'wsdl uri' field was modified **not** to have "?wsdl" string. i.e wsdl
uri = [http://localhost:8080/WsSecurity10/X10](http://localhost:8080/WsSecurity10/X10) instead of
[http://localhost:8080/WsSecurity10/X10?wsdl](http://localhost:8080/WsSecurity10/X10?wsdl).
The test failed with :
ERROR: System.InvalidOperationException: The HTML document does not contain Web
service discovery information.
at System.Web.Services.Discovery.DiscoveryClientProtocol.DiscoverAny(String url)

Next, the svcutil tool (from the Windows SDK) was used to obtain the service
proxy on the MS client side. This time the error message contained more detail :

---------------------------------------------------
Microsoft (R) Service Model Metadata Tool
[Microsoft (R) Windows (R) Communication Foundation, Version 3.0.4312.0]
Copyright (c) Microsoft Corporation. All rights reserved.

Attempting to download metadata from 'http://localhost:8080/WsSecurity10/X10'
using WS-Metadata Exchange or DISCO.
Microsoft (R) Service Model Metadata Tool
[Microsoft (R) Windows (R) Communication Foundation, Version 3.0.4312.0]
Copyright (c) Microsoft Corporation. All rights reserved.

Error: Cannot obtain Metadata from [http://localhost:8080/WsSecurity10/X10](http://localhost:8080/WsSecurity10/X10)

If this is a Windows (R) Communication Foundation service to which you have
access, please check that you have enabled metadata publishing at the specified
address. For help enabling metadata publishing, please refer to the MSDN
documentation at [http://go.microsoft.com/fwlink/?LinkId=65455](http://go.microsoft.com/fwlink/?LinkId=65455).

WS-Metadata Exchange Error
URI: [http://localhost:8080/WsSecurity10/X10](http://localhost:8080/WsSecurity10/X10)

Metadata contains a reference that cannot be resolved:
'http://localhost:8080/WsSecurity10/X10'.

Sendera:InvalidMessageInformationHeadera:InvalidMessageInformationHeaderA message information header is not valid and the message
cannot be processed.ns2:Action

HTTP GET Error
URI: [http://localhost:8080/WsSecurity10/X10](http://localhost:8080/WsSecurity10/X10)

The HTML document does not contain Web service discovery information.

----------------------------------------------------

It appears MEX is being used [ see the 'WS-Metadata Exchange Error'
message].However , looks like "?wsdl" is mandated to be there too.
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[current]

Source: [https://github.com/javaee/metro-wsit/issues/486](https://github.com/javaee/metro-wsit/issues/486)
Author: glassfishrobot

Start with the attached WsSecurity10.war and the client- and server-side log snippets, then reproduce the MS-to-Sun interop request against the listed X10 endpoint with and without the ?wsdl suffix. Compare the MEX and HTTP GET failures; done means the reported metadata exchange succeeds for the endpoint form described and the relevant interop check passes.

Written by the indexing model from the issue text.