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

[glassfishrobot]

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 instead of 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

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.

WS-Metadata Exchange Error URI: http://localhost:8080/WsSecurity10/X10

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

<?xml version="1.0" encoding="utf-16"?><Fault xmlns="http://www.w3.org/2003/05/soap-envelope">Sender<Value xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing">a:InvalidMessageInformationHeader<Value xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing">a:InvalidMessageInformationHeader<Text xml:lang="en-US">A message information header is not valid and the message cannot be processed.<Detail xmlns:env="http://www.w3.org/2003/05/soap-envelope"><ns2:ProblemHeaderQName xmlns:ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing">ns2:Action</ns2:ProblemHeaderQName>

HTTP GET Error URI: 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]

[glassfishrobot]

Reported by eric_ekka@java.net

[glassfishrobot]

eric_ekka@java.net said: Created an attachment (id=318) client side commandline log

[glassfishrobot]

eric_ekka@java.net said: Created an attachment (id=319) server log snip

[glassfishrobot]

eric_ekka@java.net said: Created an attachment (id=320) service war

[glassfishrobot]

bbissett@java.net said: Am reassigning to "owner of selected subcomponent." If that turns out to be me again, then I need to figure out how to change the issue tracker settings for wsit.

[glassfishrobot]

bbissett@java.net said: Re-reassigning.

[glassfishrobot]

hofsass@java.net said: Issue is that Addressing Pipe rejects incoming MEX request because it uses Addressing version different from that of the endpoint.

e.g. Client -(MEX request with W3C WSA headers)-> Endpoint (using MemSub/2004 Addressing)

Endpoint rejects incoming MEX request.

A simple fix would be to switch the order of the Addr & MEX pipes (i.e. make MEX first) and MEX call into some Addressing utility functions for the minimal Addressing support it really needs.

Another fix is given MEX resource its own endpoint... which is also likely needed for MTOM, etc. support.

Trying to up priority to P2

This bug is the same issue as #506, which I will close as a dup.

[glassfishrobot]

hofsass@java.net said:

• • • Issue 506 has been marked as a duplicate of this issue. ***

[glassfishrobot]

hofsass@java.net said: Setting to p3 from p2 - not critical for WSIT M5. Do have a fix which is under review and expect to be checked in shortly.

[glassfishrobot]

hofsass@java.net said: Added keyword as91-na

[glassfishrobot]

ritzmann@java.net said: Not clear how to fix this.

[glassfishrobot]

ritzmann@java.net said: Taking issue, resetting status, waving for AS 9.1.1.

[glassfishrobot]

ritzmann@java.net said: push out target milestone

[glassfishrobot]

ritzmann@java.net said: .

[glassfishrobot]

@mpotociar said: Updated fixed version field

[glassfishrobot]

File: server-mex.log Attached By: eric_ekka@java.net

[glassfishrobot]

File: svcutil-error.txt Attached By: eric_ekka@java.net

[glassfishrobot]

File: WsSecurity10.war Attached By: eric_ekka@java.net

[glassfishrobot]

Was assigned to snajper

[glassfishrobot]

This issue was imported from java.net JIRA WSIT-486