WSDL Import from web service using a http proxy server

Hello,

I have aan annoying problem creating a Web Service Consumer using 8.5 (or 8.02).

My Problem is, the target Web Service is accessible via a http proxy only.

After setting up the proxy in the location document I can manually fetch the WSDL in the integrated web browser. But the import functionality (create Web Service Consumer in Designer client) for WSDLs allways times out.

I then sniffed on the line and found that the designer tries to get the WSDL directly from the Web server ignoring the proxy setting.

Is there a way to use the WSDL import function with a proxy or is it a bug ?

Importing another directly accessible Web Service runs without problems.

Thanks a lot,

Thomas

Subject: Bugs identified

Meanwhile I could drill a little bit deeper into the problem.The WSDL Import can handle proxy settings.

It fetches the WSDL xml via proxy - Ok.

But if the WSDL xml references an XSD via URL,

the import process does NOT use the proxy.

Annoying.

I manually downloaded the WSDL and XSD xml and modified the references to the local files.

Then these files could be imported successfully.

Of course I had to shorten some Identifiers in the

WSDL due to the Lotus Script identifier limitation.

Hope this experience is helpful for someone else.

Greetings

Thomas

Subject: Please Help

Hi Thomas

I have same problem how can i solve this. WSDL page under how can i edit


<?xml version="1.0" encoding="UTF-8"?>

xsd:schema

<xsd:import schemaLocation=“http://10.6.240.60:8080/xxefa_registered_users_ws_pkg/XXEFA_REGISTERED_USERS_WS_PKG?xsd=1” namespace=“http://ws.xxtg/”/></xsd:schema>

<soap:binding style=“document” transport=“http://schemas.xmlsoap.org/soap/http”/>

<soap:operation soapAction=“”/> <soap:body use=“literal”/>

<soap:body use=“literal”/>

<soap:address location=“http://10.6.240.60:8080/xxefa_registered_users_ws_pkg/XXEFA_REGISTERED_USERS_WS_PKG”/>