Https and wsdl

[John Landon]

Hi,
You might push back on this question because it's not real java question but:
I have a java jax-ws service on tomcat.
Until now it was running on http.
I want to move it to https.
So,
I followed these instructions for creating a .keystore file
ssl tomcat
I get to my wsdl via the browser and I see it:
https://localhost:8443/services/WebService?wsdl
but my client is c#. So for creating a stub I am using their wsdl utility.
On http everything was fine but now:
I tried to do:
wsdl https://localhost:8443/services/WebService?wsdl

I got:

Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved.
Error: There was an error processing 'https://localhost:8443/services/WebService
?wsdl'.
  - There was an error downloading 'https://localhost:8443/services/WebService?w
sdl'.
  - The underlying connection was closed: Could not establish trust relationship
 for the SSL/TLS secure channel.
  - The remote certificate is invalid according to the validation procedure.
 
If you would like more help, please type "wsdl /?".

what does this mean? I can access the wsdl via the browser!

I tried to download the wsdl and ran: wsdl WebService.wsdl
What I got is:

Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved.
Error: Cannot find definition for <a href="http://webservices.abc.com:WebServic" target="_blank" rel="nofollow">http://webservices.abc.com:WebServic</a>
eEndpointInterface.  Service Description with namespace <a href="http://webservices.abc.com" target="_blank" rel="nofollow">http://webservices.abc.com</a> is missing.
Parameter name: name
 
If you would like more help, please type "wsdl /?".

Why this doesn't work now?

Thanks.

[Peer Reynders]

Originally posted by John Landon:
it's not real java question but

You might be surprised what is "real" when it comes to SOAP web services.

(java.sun.com) The WSIT Tutorial: Developing a Microsoft .NET Client

Could not establish trust relationship for the SSL/TLS secure channel. - The remote certificate is invalid according to the validation procedure.

That problem is discussed here: SVCUTIL SSL Could not establish trust relationship

Obviously there is a difference in the way svcutil and your browser deal with these types of errors. You employed the obvious work-around - make a local copy of the WSDL.

Cannot find definition for http://webservices.abc.com:WebServiceEndpointInterface. Service Description with namespace http://webservices.abc.com is missing. Parameter name: name

Basically the tool is saying that the WSDL is incomplete. Playing around with Java 6 JAX-WS I've seen some strange things in the published WSDLs. When I cobbled together the example for the Confusion in writing web service client + jax-ws topic I noticed:

the default namespace of "http://schemas.xmlsoap.org/wsdl/" is never declared in the WSDL- it is simply assumed.

The namespace for the "xsd" prefix is never declared - it is simply assumed to be "http://www.w3.org/2001/XMLSchema"

The namespace for the "tns" prefix is never declared - it is simply assumed to be identical to the targetNamespace.

The namespace for the "soap" prefix is never declared - it is simply assumed to be "http://schemas.xmlsoap.org/wsdl/soap/".

My guess is that the definitions element in the copy of the WSDL needs to be changed to something like:

<definitions 
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:tns="http://webservices.abc.com"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    targetNamespace="http://webservices.abc.com" 
    name="WebServiceEndpoint">

but I can't be sure without seeing the WSDL.

As for getting the C# SOAP web service client to work with SSL I suggest that you poke around the MSDN.
[ November 21, 2008: Message edited by: Peer Reynders ]

[John Landon]

Thanks a lot for such wide answer. But I used the wsdl utility (I don't even have the svcutil utility
[ November 21, 2008: Message edited by: John Landon ]

[John Landon]

Here is my jax-ws.xml:

 <endpoints xmlns="http://java.sun.com/xml/ns/jax-ws/ri/runtime" version="2.0">
 
    <endpoint
            name='WebServiceEndpointInterface'
            implementation='com.abc.webservices.WebServiceEndpointImpl'
            url-pattern='/services/WebService'>
    </endpoint>
</endpoints>   

here is the wsdl:

<?xml version="1.0" encoding="UTF-8" ?> 
- <!--  Published by JAX-WS RI at <a href="http://jax-ws.dev.java.net." target="_blank" rel="nofollow">http://jax-ws.dev.java.net.</a> RI's version is JAX-WS RI 2.1.4-b01-. 
  --> 
- <!--  Generated by JAX-WS RI at <a href="http://jax-ws.dev.java.net." target="_blank" rel="nofollow">http://jax-ws.dev.java.net.</a> RI's version is JAX-WS RI 2.1.4-b01-. 
  --> 
- <definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://webservices.abc.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://webservices.abc.com/" name="WebServiceEndpointImplService">
  <import namespace="http://webservices.abc.com" location="https://localhost:8443/services/WebService?wsdl=1" /> 
- <binding xmlns:ns1="http://webservices.abc.com" name="WebServiceEndpointImplPortBinding" type="ns1:WebServiceEndpointInterface">
  <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /> 
- <operation name="communicate">
  <soap :-o	 peration soapAction="" /> 
- <input>
  <soap:body use="literal" /> 
  </input>
- <output>
  <soap:body use="literal" /> 
  </output>
  </operation>
  </binding>
- <service name="WebServiceEndpointImplService">
- <port name="WebServiceEndpointImplPort" binding="tns:WebServiceEndpointImplPortBinding">
  <soap:address location="https://localhost:8443/services/WebService" /> 
  </port>
  </service>
  </definitions>    

Thanks a lot.

[Peer Reynders]

svcutil.exe is part of the Windows SDK. wsdl.exe is part of Visual Studio. The issues remain the same.

[Peer Reynders]

For completeness sake
https://localhost:8443/services/WebService?wsdl=1
is also needed. That is what the tool is missing.

So you need to make a local copy of "wsdl=1" and change the local copy of the WSDL to point to your local copy through its "location" attribute in the import element.

[John Landon]

So what do I do? I just need to do it once

[John Landon]

I did what you said:
wsdl:

   <?xml version="1.0" encoding="UTF-8"?><!-- Published by JAX-WS RI at <a href="http://jax-ws.dev.java.net." target="_blank" rel="nofollow">http://jax-ws.dev.java.net.</a> RI's version is JAX-WS RI 2.1.4-b01-. --><!-- Generated by JAX-WS RI at <a href="http://jax-ws.dev.java.net." target="_blank" rel="nofollow">http://jax-ws.dev.java.net.</a> RI's version is JAX-WS RI 2.1.4-b01-. --><definitions xmlns:tns="http://webservices.abc.com" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://webservices.abc.com">
<types>
<xsd:schema>
<xsd:import namespace="http://webservices.abc.com" schemaLocation="https://localhost:8443/services/WebService?xsd=1"></xsd:import>
</xsd:schema>
</types>
<message name="communicate">
<part name="parameters" element="tns:communicate"></part>
</message>
<message name="communicateResponse">
<part name="parameters" element="tns:communicateResponse"></part>
</message>
<portType name="WebServiceEndpointInterface">
<operation name="communicate">
<input message="tns:communicate"></input>
<output message="tns:communicateResponse"></output>
</operation>
</portType>
</definitions> 

then I ran wsdl WebService.wsdl
and I got:

  Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved.
Warning: This web reference does not conform to WS-I Basic Profile v1.1.
SOAP 1.1 binding was not found: WS-I's Basic Profile 1.1 consists of implementat
ion guidelines that recommend how a set of core Web services specifications shou
ld be used together to develop interoperable Web services. For the 1.1 Profile,
those specifications are SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0 and XML Schema.
 
For more details on the WS-I Basic Profile v1.1, see the specification
at <a href="http://www.ws-i.org/Profiles/BasicProfile-1.1.html." target="_blank" rel="nofollow">http://www.ws-i.org/Profiles/BasicProfile-1.1.html.</a>
 
Warning: no classes were generated.
Warnings were encountered. Review generated source comments for more details.
 
Writing file 'C:\Documents and Settings\abc\output.cs'.  

[Peer Reynders]

You have in your local WebService.wsdl:

<import namespace="http://webservices.abc.com" location="https://localhost:8443/services/WebService?wsdl=1" /> 

With the browser access "https://localhost:8443/services/WebService?wsdl=1" and "Save As" "WebService1.wsdl" in the same directory where "WebService.wsdl" is.

Then modify your local WebService.wsdl:

<import namespace="http://webservices.abc.com" location="WebService1.wsdl" /> 

Open a console window; change your working directory to the one that contains WebService.wsdl and WebService1.wsdl. Run wsdl.exe on WebService.wsdl.
[ November 21, 2008: Message edited by: Peer Reynders ]

[John Landon]

same thing:

  Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved.
Error: Cannot find definition for <a href="http://webservices.abc.com:WebServic" target="_blank" rel="nofollow">http://webservices.abc.com:WebServic</a>
eEndpointInterface.  Service Description with namespace <a href="http://webservices.abc.com" target="_blank" rel="nofollow">http://webservices.abc.com</a> is missing.
Parameter name: name
 
If you would like more help, please type "wsdl /?".  

[Peer Reynders]

The contents of https://localhost:8443/services/WebService?wsdl=1 may help to shed some light on the matter. It may be referencing another schema - or the tool isn't picking up the local WebService1.wsdl in which case one could build a single wsdl file. But for that it is necessary to see all of the referenced WSDL files and XML Schemas that are published by the web service.
[ November 21, 2008: Message edited by: Peer Reynders ]

[John Landon]

WebService1.wsdl:

  <?xml version="1.0" encoding="UTF-8"?><!-- Published by JAX-WS RI at <a href="http://jax-ws.dev.java.net." target="_blank" rel="nofollow">http://jax-ws.dev.java.net.</a> RI's version is JAX-WS RI 2.1.4-b01-. --><!-- Generated by JAX-WS RI at <a href="http://jax-ws.dev.java.net." target="_blank" rel="nofollow">http://jax-ws.dev.java.net.</a> RI's version is JAX-WS RI 2.1.4-b01-. --><definitions xmlns:tns="http://webservices.abc.com" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://webservices.abc.com">
<types>
<xsd:schema>
<xsd:import namespace="http://webservices.abc.com" schemaLocation="https://localhost:8443/services/WebService?xsd=1"></xsd:import>
</xsd:schema>
</types>
<message name="communicate">
<part name="parameters" element="tns:communicate"></part>
</message>
<message name="communicateResponse">
<part name="parameters" element="tns:communicateResponse"></part>
</message>
<portType name="WebServiceEndpointInterface">
<operation name="communicate">
<input message="tns:communicate"></input>
<output message="tns:communicateResponse"></output>
</operation>
</portType>
</definitions>  

WebService.wsdl:

  <?xml version="1.0" encoding="UTF-8"?><!-- Published by JAX-WS RI at <a href="http://jax-ws.dev.java.net." target="_blank" rel="nofollow">http://jax-ws.dev.java.net.</a> RI's version is JAX-WS RI 2.1.4-b01-. --><!-- Generated by JAX-WS RI at <a href="http://jax-ws.dev.java.net." target="_blank" rel="nofollow">http://jax-ws.dev.java.net.</a> RI's version is JAX-WS RI 2.1.4-b01-. --><definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://webservices.abc.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://webservices.abc.com/" name="WebServiceEndpointImplService">
<import namespace="http://webservices.abc.com" location="WebService1.wsdl"></import>
<binding xmlns:ns1="http://webservices.abc.com" name="WebServiceEndpointImplPortBinding" type="ns1:WebServiceEndpointInterface">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"></soap:binding>
<operation name="communicate">
<soap    :-o	    peration soapAction=""></soap    :-o	    peration>
<input>
<soap:body use="literal"></soap:body>
</input>
<output>
<soap:body use="literal"></soap:body>
</output>
</operation>
</binding>
<service name="WebServiceEndpointImplService">
<port name="WebServiceEndpointImplPort" binding="tns:WebServiceEndpointImplPortBinding">
<soap:address location="https://localhost:8443/services/WebService"></soap:address>
</port>
</service>
</definitions>  

WebService1.xsd:

  <?xml version="1.0" encoding="UTF-8"?><!-- Published by JAX-WS RI at <a href="http://jax-ws.dev.java.net." target="_blank" rel="nofollow">http://jax-ws.dev.java.net.</a> RI's version is JAX-WS RI 2.1.4-b01-. --><xs:schema xmlns:tns="http://webservices.abc.com" xmlns:xs="http://www.w3.org/2001/XMLSchema" version="1.0" targetNamespace="http://webservices.abc.com">
 
<xs:element name="communicate" type="tns:communicate"></xs:element>
 
<xs:element name="communicateResponse" type="tns:communicateResponse"></xs:element>
 
<xs:complexType name="communicate">
<xs:sequence>
<xs:element name="arg0" type="xs:string" minOccurs="0"></xs:element>
<xs:element name="arg1" type="xs:anyType" minOccurs="0"></xs:element>
</xs:sequence>
</xs:complexType>
 
<xs:complexType name="communicateResponse">
<xs:sequence>
<xs:element name="return" type="xs:anyType" minOccurs="0"></xs:element>
</xs:sequence>
</xs:complexType>
</xs:schema>  

The message I get after running wsdl WebService.wsdl:

  Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved.
Error: Cannot find definition for <a href="http://webservices.abc.com:WebServic" target="_blank" rel="nofollow">http://webservices.abc.com:WebServic</a>
eEndpointInterface.  Service Description with namespace <a href="http://webservices.abc.com" target="_blank" rel="nofollow">http://webservices.abc.com</a> is missing.
Parameter name: name
 
If you would like more help, please type "wsdl /?".  

[ November 21, 2008: Message edited by: John Landon ]

[ November 21, 2008: Message edited by: John Landon ]
[ November 21, 2008: Message edited by: John Landon ]

[Peer Reynders]

[EDIT: replaced potentially incorrect single file with corrected set of multiple files]

This set of files compiles cleanly with wsimport - so give them a go with wsdl.exe.

WebService.xsd

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
    xmlns:tns="http://webservices.abc.com"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    version="1.0"
    targetNamespace="http://webservices.abc.com">
 
  <xs:element name="communicate" type="tns:communicate" />
  <xs:element name="communicateResponse" type="tns:communicateResponse" />
 
  <xs:complexType name="communicate">
     <xs:sequence>
       <xs:element name="arg0" type="xs:string" minOccurs="0" />
       <xs:element name="arg1" type="xs:anyType" minOccurs="0" />
     </xs:sequence>
  </xs:complexType>
 
  <xs:complexType name="communicateResponse">
    <xs:sequence>
      <xs:element name="return" type="xs:anyType" minOccurs="0" />
    </xs:sequence>
  </xs:complexType>
</xs:schema>   

WebService1.wsdl

<?xml version="1.0" encoding="UTF-8"?>
<definitions
    xmlns:tns="http://webservices.abc.com"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    targetNamespace="http://webservices.abc.com">
  <types>
    <xsd:schema>
      <xsd:import namespace="http://webservices.abc.com" schemaLocation="WebService.xsd"/>
    </xsd:schema>
  </types>
  <message name="communicate">
    <part name="parameters" element="tns:communicate" />
  </message>
  <message name="communicateResponse">
    <part name="parameters" element="tns:communicateResponse" />
  </message>
  <portType name="WebServiceEndpointInterface">
    <operation name="communicate">
      <input message="tns:communicate" />
      <output message="tns:communicateResponse" />
    </operation>
  </portType>
</definitions>  

WebService.wsdl

<?xml version="1.0" encoding="UTF-8"?>
<definitions
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:tns="http://webservices.abc.com/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    targetNamespace="http://webservices.abc.com/"
    name="WebServiceEndpointImplService">
  <import namespace="http://webservices.abc.com" location="WebService1.wsdl" />
  <binding
      xmlns:ns1="http://webservices.abc.com"
      name="WebServiceEndpointImplPortBinding"
      type="ns1:WebServiceEndpointInterface">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
    <operation name="communicate">
      <soap:operation soapAction="" />
      <input>
        <soap:body use="literal" />
      </input>
      <output>
        <soap:body use="literal" />
      </output>
    </operation>
  </binding>
  <service
      name="WebServiceEndpointImplService">
    <port
        name="WebServiceEndpointImplPort"
        binding="tns:WebServiceEndpointImplPortBinding">
      <soap:address location="https://localhost:8443/services/WebService" />
    </port>
  </service>
</definitions>

[ November 21, 2008: Message edited by: Peer Reynders ]

[John Landon]

Thanks but it's still the same:
Cannot find definition for http://webservices.abc.com:WebServiceEndpointInterface. Service Description with namespace http://webservices.abc.com is missing. Parameter name: name

[Peer Reynders]

Originally posted by John Landon:
Thanks but it's still the same:
Cannot find definition for http://webservices.abc.com:WebServiceEndpointInterface.

It seems that wsdl.exe is having problems with the WSDL import statement.
WebService.wsdl defines the service in the "http://webservices.abc.com/" namespace.
WebService1.wsdl defines the types that the service is based on in the "http://webservices.abc.com" namespace - note the missing backslash at the end.

Either wsdl.exe can't read WebService1.wsdl at all or it mistakenly carries over the enclosing targetnamespace through the WDSL import - which would cause it define
{http://webservices.abc.com/}WebServiceEndpointInterface
rather than
{http://webservices.abc.com}WebServiceEndpointInterface

Is this an older version of .NET/Visual Studio?
[ November 24, 2008: Message edited by: Peer Reynders ]

[John Landon]

2005 c# express

[Peer Reynders]

wsdl.exe Doesn't Resolve <import>'s

So try

wsdl WebService.wsdl WebService1.wsdl WebService.xsd

[John Landon]

WORKED!
Thanks. A LOT!
now fighting with certificates

Thanks again