Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 164245

Summary:

Unable to open a WSDL provided via URL in web services explorer

Product:

[WebTools] WTP Webservices

Reporter:

Bill Klish <bkbugzilla>

Component:

wst.ws

Assignee:

Chris Brealey <cbrealey>

Status:

CLOSED DUPLICATE

QA Contact:

Chris Brealey <cbrealey>

Severity:

major

Priority:

CC:

gilberta, wxu

Version:

1.5

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
Screenshot of WSE after clicking on the "lookup" operation	none

Description Bill Klish

2006-11-11 19:20:27 EST

I have downloaded all of the latest components for Eclipse and WTP 1.5.2.  I am trying to open a WSDL using http in the web services explorer.  I type in my WSDL address and hit go.  I see one progress bar show up in the bottom of the window and then nothing happens.  I tried starting eclipse with -debug and -consolelog but don't see anything being logged.  

I have tried with 3 different WSDLs but nothing happens.  I removed the ?WSDL from the URL and it throws an invalid WSDL exception, so something is working.

In Eclipse 3.1, and WTP 1.0 this works without a problem.

Comment 1 Richard Mah

2007-01-05 14:29:48 EST

Chris, could you please take a look?  Thanks.

Comment 2 Chris Brealey

2007-01-05 15:00:38 EST

Bill,
which JRE or JDK are you using? The WSE has been known to get upset about the Crimson parser in J2SE 1.4.2, and in a way I'm reminded of by the symptom you described.

If you download a copy of the WSDL into your workspace and try to load that instead of the original ...?WSDL, do you get any different behaviour? Do you have a WSDL document you can attach to this bug for us to try?

Thanks - CB.

Comment 3 Xu Wei

2007-05-10 23:26:50 EDT

We have wsdl file and generated by Weblogic. The part content is following.
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="BookFinderServiceDefinitions" targetNamespace="http://com/vitria/hellowstutorial" xmlns:s2="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s0="http://www.w3.org/2001/XMLSchema" xmlns:s1="http://com/vitria/hellowstutorial" xmlns="http://schemas.xmlsoap.org/wsdl/">
  <types>
  </types>
  <message name="lookupResponse">
    <part name="lookupReturn" type="s0:string"/>
  </message>
  <message name="lookup">
    <part name="lookup_ParamA" type="s0:string"/>
    <part name="lookup_ParamB" type="s0:string"/>
  </message>
  <portType name="BookFinder">
    <operation name="lookup" parameterOrder="lookup_ParamA lookup_ParamB">
      <input message="s1:lookup"/>
      <output message="s1:lookupResponse"/>
    </operation>
  </portType>
  <binding name="BookFinderServiceSoapBinding" type="s1:BookFinder">
    <s2:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="lookup">
      <s2:operation soapAction="" style="rpc"/>
      <input>
        <s2:body parts="lookup_ParamA lookup_ParamB" use="literal" namespace="http://com/vitria/hellowstutorial"/>
      </input>
      <output>
        <s2:body parts="lookupReturn" use="literal" namespace="http://com/vitria/hellowstutorial"/>
      </output>
    </operation>
  </binding>
  <service name="BookFinderService">
    <port name="BookFinderSoapPort" binding="s1:BookFinderServiceSoapBinding">
      <s2:address location="http://localhost:7001/HelloWebServicesApplication/HelloWebServices_MainIM_ServiceProxy/BookFinder"/>
    </port>
  </service>
</definitions>


When I open the url (http://pek-wkst220.qilinsoftcorp.qilinsoft.com:8080/eProxy/service/BookFinderSoapPort_Proxy?wsdl <http://pek-wkst220.qilinsoftcorp.qilinsoft.com:8080/eProxy/service/BookFinderSoapPort_Proxy?wsdl>  <http://pek-wkst220.qilinsoftcorp.qilinsoft.com:8080/eProxy/service/BookFinderSoapPort_Proxy?wsdl <http://pek-wkst220.qilinsoftcorp.qilinsoft.com:8080/eProxy/service/BookFinderSoapPort_Proxy?wsdl> >  on my system) in the Web Services Explorer, click "lookup" item on left navigate window, then there will appear an white page without any component on page.

Comment 4 Xu Wei

2007-05-10 23:27:17 EDT

We have wsdl file and generated by Weblogic. The part content is following.
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="BookFinderServiceDefinitions" targetNamespace="http://com/vitria/hellowstutorial" xmlns:s2="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s0="http://www.w3.org/2001/XMLSchema" xmlns:s1="http://com/vitria/hellowstutorial" xmlns="http://schemas.xmlsoap.org/wsdl/">
  <types>
  </types>
  <message name="lookupResponse">
    <part name="lookupReturn" type="s0:string"/>
  </message>
  <message name="lookup">
    <part name="lookup_ParamA" type="s0:string"/>
    <part name="lookup_ParamB" type="s0:string"/>
  </message>
  <portType name="BookFinder">
    <operation name="lookup" parameterOrder="lookup_ParamA lookup_ParamB">
      <input message="s1:lookup"/>
      <output message="s1:lookupResponse"/>
    </operation>
  </portType>
  <binding name="BookFinderServiceSoapBinding" type="s1:BookFinder">
    <s2:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="lookup">
      <s2:operation soapAction="" style="rpc"/>
      <input>
        <s2:body parts="lookup_ParamA lookup_ParamB" use="literal" namespace="http://com/vitria/hellowstutorial"/>
      </input>
      <output>
        <s2:body parts="lookupReturn" use="literal" namespace="http://com/vitria/hellowstutorial"/>
      </output>
    </operation>
  </binding>
  <service name="BookFinderService">
    <port name="BookFinderSoapPort" binding="s1:BookFinderServiceSoapBinding">
      <s2:address location="http://localhost:7001/HelloWebServicesApplication/HelloWebServices_MainIM_ServiceProxy/BookFinder"/>
    </port>
  </service>
</definitions>


When I open the url (http://pek-wkst220.qilinsoftcorp.qilinsoft.com:8080/eProxy/service/BookFinderSoapPort_Proxy?wsdl <http://pek-wkst220.qilinsoftcorp.qilinsoft.com:8080/eProxy/service/BookFinderSoapPort_Proxy?wsdl>  <http://pek-wkst220.qilinsoftcorp.qilinsoft.com:8080/eProxy/service/BookFinderSoapPort_Proxy?wsdl <http://pek-wkst220.qilinsoftcorp.qilinsoft.com:8080/eProxy/service/BookFinderSoapPort_Proxy?wsdl> >  on my system) in the Web Services Explorer, click "lookup" item on left navigate window, then there will appear an white page without any component on page.

Comment 5 Xu Wei

2007-05-10 23:30:49 EDT

we are also having similar issue and check if there is any workaround.
We have wsdl file and generated by Weblogic. The part content is following.
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="BookFinderServiceDefinitions" targetNamespace="http://com/vitria/hellowstutorial" xmlns:s2="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s0="http://www.w3.org/2001/XMLSchema" xmlns:s1="http://com/vitria/hellowstutorial" xmlns="http://schemas.xmlsoap.org/wsdl/">
  <types>
  </types>
  <message name="lookupResponse">
    <part name="lookupReturn" type="s0:string"/>
  </message>
  <message name="lookup">
    <part name="lookup_ParamA" type="s0:string"/>
    <part name="lookup_ParamB" type="s0:string"/>
  </message>
  <portType name="BookFinder">
    <operation name="lookup" parameterOrder="lookup_ParamA lookup_ParamB">
      <input message="s1:lookup"/>
      <output message="s1:lookupResponse"/>
    </operation>
  </portType>
  <binding name="BookFinderServiceSoapBinding" type="s1:BookFinder">
    <s2:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="lookup">
      <s2:operation soapAction="" style="rpc"/>
      <input>
        <s2:body parts="lookup_ParamA lookup_ParamB" use="literal" namespace="http://com/vitria/hellowstutorial"/>
      </input>
      <output>
        <s2:body parts="lookupReturn" use="literal" namespace="http://com/vitria/hellowstutorial"/>
      </output>
    </operation>
  </binding>
  <service name="BookFinderService">
    <port name="BookFinderSoapPort" binding="s1:BookFinderServiceSoapBinding">
      <s2:address location="http://localhost:7001/HelloWebServicesApplication/HelloWebServices_MainIM_ServiceProxy/BookFinder"/>
    </port>
  </service>
</definitions>


When I open the url (http://pek-wkst220.qilinsoftcorp.qilinsoft.com:8080/eProxy/service/BookFinderSoapPort_Proxy?wsdl <http://pek-wkst220.qilinsoftcorp.qilinsoft.com:8080/eProxy/service/BookFinderSoapPort_Proxy?wsdl>  <http://pek-wkst220.qilinsoftcorp.qilinsoft.com:8080/eProxy/service/BookFinderSoapPort_Proxy?wsdl <http://pek-wkst220.qilinsoftcorp.qilinsoft.com:8080/eProxy/service/BookFinderSoapPort_Proxy?wsdl> >  on my system) in the Web Services Explorer, click "lookup" item on left navigate window, then there will appear an white page without any component on page.

Comment 6 Chris Brealey

2007-05-11 11:10:20 EDT

Created attachment 66872 [details]
Screenshot of WSE after clicking on the "lookup" operation

Xu, your last three comments look very similar to each other, so I'm not sure if I'm missing any key differences between them. In any event, I copied the WSDL from your comment into a WSDL file in WTP 1.5.4, then opened it in the Web Services Explorer. Clicking on the WSDL's "lookup" operation results for me in what looks like a correct input form. Please have a look at this screenshot and let me know if you're getting something different in the Actions pane. Would you please also retry your scenario using WTP 1.5.4?

Comment 7 zhiliang chen

2007-05-16 02:10:04 EDT

please try this wsdl, it is the wsdl get the problem, thank you

<?xml version="1.0" encoding="UTF-8"?>
<definitions name="BookFinderServiceDefinitions" targetNamespace="http://com/vitria/hellowstutorial" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s0="http://www.w3.org/2001/XMLSchema" xmlns:s1="http://com/vitria/hellowstutorial" xmlns:s2="http://schemas.xmlsoap.org/wsdl/soap/">
  <types>
  </types>
  <message name="lookupResponse">
    <part name="lookupReturn" type="s0:string"/>
  </message>
  <message name="lookup">
    <part name="lookup_ParamA" type="s0:string"/>
    <part name="lookup_ParamB" type="s0:string"/>
  </message>
  <portType name="BookFinder">
    <operation name="lookup" parameterOrder="lookup_ParamA lookup_ParamB">
      <input message="s1:lookup"/>
      <output message="s1:lookupResponse"/>
    </operation>
  </portType>
  <binding name="BookFinderServiceSoapBinding" type="s1:BookFinder">
    <s2:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="lookup">
      <s2:operation soapAction="" style="rpc"/>
      <input>
        <s2:body namespace="http://com/vitria/hellowstutorial" parts="lookup_ParamA lookup_ParamB" use="literal"/>
      </input>
      <output>
        <s2:body namespace="http://com/vitria/hellowstutorial" parts="lookupReturn" use="literal"/>
      </output>
    </operation>
  </binding>
  
<wsdl:service name="BookFinderService" xmlns:apwsdl="urn:com.amberpoint.wsdl" xmlns:e="http://com.amberpoint.messaging/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"><wsdl:port binding="s1:BookFinderServiceSoapBinding" name="BookFinderSoapPort"><soap:address location="http://pek-wkst220.qilinsoftcorp.qilinsoft.com:8080/eProxy/service/BookFinderSoapPort_Proxy"/><apwsdl:targetWSDL><apwsdl:URL>http://pek-wkst220.qilinsoftcorp.qilinsoft.com:7001/HelloWebServicesApplication/ServiceProxy.wsdl</apwsdl:URL><apwsdl:agentID>uuid:CB9B8A1C-036F-11DC-B6CD-54C46AA1AA77</apwsdl:agentID><apwsdl:uwsID>uuid:CF9FAC93-0370-11DC-B6CD-54C46AA1AA77</apwsdl:uwsID><apwsdl:uwsLocalname>BookFinderSoapPort_Proxy</apwsdl:uwsLocalname></apwsdl:targetWSDL></wsdl:port></wsdl:service></definitions>

Comment 8 Chris Brealey

2007-05-16 11:08:12 EDT

Thanks - I've reproduced the problem, and found that specifically changing "soap:address" to "s2:address", thus referring to the namespace prefix defined on the <definitions> element instead of the <service> element, works around the issue. This is a duplicate of bug 175842. The problem is in WSDL4J.

*** This bug has been marked as a duplicate of bug 175842 ***

Comment 9 Kathy Chan

2007-05-25 12:46:03 EDT

Please take a moment to verify and close WTP defects using WTP 2.0 RC1:

http://download.eclipse.org/webtools/downloads/drops/R2.0/S-2.0RC1-200705250432/

Comment 10 Kathy Chan

2007-06-13 13:31:09 EDT

We are closing down the WTP 2.0 release pretty soon, please verify these defects with the latest WTP 2.0 build.  The WTP 2.0 RC2 driver is available at:

http://download.eclipse.org/webtools/downloads/drops/R2.0/S-2.0RC2-200706050057/

Comment 11 Chris Brealey

2007-06-13 13:38:11 EDT

Closed as duplicate on behalf of submitter.