Inaccessible WSDL error revisited

Hi,

I have a Java application written using a WSimport-ed JAR that I got from a local server. At the time, a big problem I had generating the WSDL was that the WSDL returned uses local host names for elements within it. This is normally not a problem since when an application is used on the LAN, the client is able to resolve that. My problem now is that the application I have written needs to connect to a Content Server instance across the internet so the local host name will not be resolvable. When I run the application, it always craps out trying to instantiate the Authentication service and responds with an InaccessibleWSDL exception. Is this a fundamental limitation of Web Services? I've googled this with not much luck as I'm doing a very vanilla app to test some functionality. It seems I need something to help me resolve the local host name returned in the WSDL to something else, but I had thought that this is only a "thing" if you're trying to do the WSImport remotely.

-Hugh Ferguson

Find more posts tagged with

Comments

AlexGerasimov

Did you try something like this?

private static final String cwsServiceUrl = "http://somewhereinthegalaxy/cws/Authentication.svc?wsdl";

..........................

       Authentication_Service auth_service = new Authentication_Service( new URL(cwsServiceUrl), new QName("urn:Core.service.livelink.opentext.com", "Authentication"));
       //Authentication_Service auth_service = new Authentication_Service();
       Authentication auth = auth_service.getBasicHttpBindingAuthentication();

       String authToken = getAuthenticationToken(auth, username, password);

       OTAuthentication otAuth = new OTAuthentication();

otAuth.setAuthenticationToken( authToken );

HFCDev

I don't have the source handy but that looks about right. As I said before, it works against an Azure server so long as you're using an Azure VPN client and you have the inward facing IP's mapped in your host file, but if you only have the externally facing URL it doesn't work.

-Hugh

HFCDev

Here is my exact function:

//********************************************************************************//* Service stubs.  Use these to get the various CWS API methods//********************************************************************************public Authentication getAuthClient() throws Exception {		if (authClient == null) {			Authentication_Service authService = new Authentication_Service(CWSUtils.getServiceURL(this.hostname, "Authentication", isTomcat), new QName(CWSUtils.CORE_NAMESPACE,"Authentication" ));			authClient = authService.getBasicHttpBindingAuthentication();		}		//debug("returning auth client");		if (authenticated) {							OTAuthentication otAuth = new OTAuthentication();			otAuth.setAuthenticationToken(authToken);			CWSUtils.setSoapHeader((WSBindingProvider) authClient, otAuth);							//debug("auth client with authentication token");		}		return authClient;	}

The main difference is the call to CWSUtils.getServiceURL(this.hostname, "Authentication", isTomcat), which is a function I added to change the URL from something like http://hostname/cws/Authentication.svc to http://hostname:8080/cws/services/Authentication depending on whether IIS or Tomcat is specified (in this case, IIS). Otherwise, the other CWSUtils functions are copied from the LLTreeView example which demonstrates how to set the various SOAP headers.

-Hugh