What can cause inaccessibility?

Question

I am updating some web service clients in some old java applications to call a third-party axis2 web service. I was provided with a wsdl file, so I developed a jar containing a client for this service, as described in the following (my) message: JAX-WS client: what is the correct way to access the local WSDL? .

It works in some application, but not in others, where it throws an inaccessibleWSDLException at the time the proxy class is instantiated. Below I posted the jax-ws-catalog file:

 <?xml version="1.0" encoding="UTF-8" standalone="no"?> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog" prefer="system"> <system systemId="http://localhost/wsdl/SOAService.wsdl" uri="wsdl/SOAService.wsdl"/> <system systemId="http://schemas.xmlsoap.org/soap/encoding/" uri="wsdl/schemas.xmlsoap.org/soap/encoding.xsd"/> <system systemId="http://www.w3.org/2005/05/xmlmime" uri="wsdl/www.w3.org/2005/05/xmlmime.xsd"/> </catalog> 

It always works inside my development environment (netbeans \ ecplise depending on the project I am updating) and servers (tomcat \ Jboss 4 \ jar with a test class).

Doesn't work when:

• I start the jar from the command line or
• I load the jar into the livecycle 8.0 process (works on jboss 4.0)

In both cases, an error message is thrown: "InaccessibleWSDLException", in particular in the life cycle, I get the following error:

 2010-12-01 12:20:47,420 ERROR [com.adobe.workflow.AWS] stalling action-instance: 9989 with message: com.sun.xml.ws.wsdl.parser.InaccessibleWSDLException: 2 counts of InaccessibleWSDLException. java.net.ConnectException: Connection refused java.net.ConnectException: Connection refused at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(RuntimeWSDLParser.java:172) at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:144) at com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:254) at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:217) at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:174) at com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:104) at javax.xml.ws.Service.<init>(Service.java:56) at com.ibm.eci.soaservice.SOAService.<init>(SOAService.java:50) 

What does this exception mean? Can't he find wsdl or part of it? He can not find the library? It cannot access the network (wsdl contains some import of external xsd)?

Answer 1

This means that livecycle 8.0 does not use or find jax-ws-catalog.xml, so jaxws runtime tries to load WSDL from the literal location specified in the client, i.e. from http: //localhost/wsdl/SOAService.wsdl instead of looking at the mapping presented in jax-ws-catalog.xml and using WSDL from your application.

The key is

java.net.ConnectException: connection rejected java.net.ConnectException: connection rejected

which tells me that jaxws runtime is trying to access WSDL via http.

Where do you put your jax-ws-catalog.xml? maybe for the life cycle, it needs to be placed somewhere else besides the JAR META-INF directory.

I think you need to post this question on the livecycle forums.

If you are not working on the command line, it is a little strange how exactly you run it from the command line.

Answer 2

It seems that it is looking for a certificate file, please check out what certificate was. Download this certificate, restart the server, and then try.

Regards, Sridhar Goranti