jax ws - What might cause a inaccessiblewsdlexception? -


i'm updating web service clients old java applications call axis2 third party web service. i've been provided wsdl file, i've developed jar containing client service described in following (mine) post: jax-ws client : what's correct path access local wsdl?.

it works on application not in others throws inaccessiblewsdlexception @ moment of instantiating proxy class. below i've posted 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 work inside development environments (netbeans\ecplise depending on project i'm updating ) , servers (tomcat \jboss 4 \ jar test class).

it doesn't work when:

  • i launch jar command line or
  • i load jar livecycle 8.0 process (runs on jboss 4.0)

in both cases gives error : "inaccessiblewsdlexception", in particular on livecycle following error :

2010-12-01 12:20:47,420 error [com.adobe.workflow.aws] stalling action-instance: 9989 message: com.sun.xml.ws.wsdl.parser.inaccessiblewsdlexception: 2 counts of inaccessiblewsdlexception.  java.net.connectexception: connection refused java.net.connectexception: connection refused          @ com.sun.xml.ws.wsdl.parser.runtimewsdlparser.trywithmex(runtimewsdlparser.java:172)         @ com.sun.xml.ws.wsdl.parser.runtimewsdlparser.parse(runtimewsdlparser.java:144)         @ com.sun.xml.ws.client.wsservicedelegate.parsewsdl(wsservicedelegate.java:254)         @ com.sun.xml.ws.client.wsservicedelegate.<init>(wsservicedelegate.java:217)         @ com.sun.xml.ws.client.wsservicedelegate.<init>(wsservicedelegate.java:174)         @ com.sun.xml.ws.spi.providerimpl.createservicedelegate(providerimpl.java:104)         @ javax.xml.ws.service.<init>(service.java:56)         @ com.ibm.eci.soaservice.soaservice.<init>(soaservice.java:50) 

what exception mean? can't find wsdl or piece of it? can't find library? can't access web (the wsdl contains import of external xsd )?

that means livecycle 8.0 not using or not finding jax-ws-catalog.xml, jaxws run-time trying load wsdl literal location mentioned in client stub, i.e. http://localhost/wsdl/soaservice.wsdl instead of looking @ mapping provided in jax-ws-catalog.xml , using wsdl application jar.

the clue

java.net.connectexception: connection refused java.net.connectexception: connection refused

which tells me jaxws runtime trying access wsdl on http.

where put jax-ws-catalog.xml ? may livecycle needs put somewhere else, besides jar's meta-inf directory.

i think need post question on livecycle forums .

for not working command line, bit strange, how run command line.


Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -