jboss5.x - org.jboss.ws.metadata.wsdl.WSDLException_ Invalid default namespace_ null -
jboss5.x - org.jboss.ws.metadata.wsdl.WSDLException_ Invalid default namespace_ null -
i have wsdl , have generated code using wsimport. have written code access web service & trying test it. works on tomcat, on jboss 5.1 ga, gives next error:
org.jboss.ws.metadata.wsdl.wsdlexception_ invalid default namespace_ null
i have spent 3 days figuring out problem no luck. 1 os solutions tried involved jaxws-rt files & working jboss endorsed directory, not sure jars need replaced, still stuck.
any help appreciated.
i guess fixed issue, in case interested.
i had same problem deploying ussd gateway mobicents jain slee, runs on top of jboss 5.1.0 ga. gateway has connect server via soap, chose jax-ws , generated source code wsdl wsimport. way, used similar procedure this one create kid maven project , generate java files jax-ws.
failed deploy dependencies embedded on .war filemy first approach include dependencies in .war file deployed in jboss. think achieved default in maven, , mvn install
it. in long run, approach failed, @ to the lowest degree needed know list of jar files included in .war file, re-create them later in jboss directory.
i made lot of troubleshooting approach, , had many different log errors, though main 1 this:
java.util.serviceconfigurationerror: javax.xml.ws.spi.provider: provider org.jboss.ws.core.jaxws.spi.providerimpl not subtype
that can found in this other stackoverflow question.
deploy without dependencies maven tweakso insted, added <scope>provided</scope>
jax-ws dependencies. like:
<dependency> <groupid>com.sun.xml.ws</groupid> <artifactid>jaxws-rt</artifactid> <version>2.2</version> <scope>provided</scope> </dependency> <dependency> <groupid>com.sun.istack</groupid> <artifactid>istack-commons-runtime</artifactid> <version>2.2</version> <scope>provided</scope> </dependency>
this produced much lighter .war file.
copy & remove jars in jboss asnow, after deploying .war file, when soap client tries connect web service, throws exception mentioned in question:
org.jboss.ws.metadata.wsdl.wsdlexception: invalid default namespace: null @ org.jboss.ws.tools.wsdl.wsdldefinitionsfactory.parse(wsdldefinitionsfactory.java:134) @ org.jboss.ws.metadata.umdm.servicemetadata.getwsdldefinitions(servicemetadata.java:293) @ org.jboss.ws.metadata.builder.jaxws.jaxwsclientmetadatabuilder.buildmetadata(jaxwsclientmetadatabuilder.java:84) @ org.jboss.ws.core.jaxws.spi.servicedelegateimpl.<init>(servicedelegateimpl.java:138) @ org.jboss.ws.core.jaxws.spi.providerimpl.createservicedelegate(providerimpl.java:63) @ javax.xml.ws.service.<init>(service.java:79) @ org.ortelius.ussdserviceimplementation.<init>(ussdserviceimplementation.java:42) @ org.ortelius.orteliusclient.sendussdrequesttows(orteliusclient.java:28)
it seems javax.xml.ws.service
calls org.jboss.ws.core.jaxws.spi.providerimpl
, should calling com.sun.xml.ws.spi.providerimpl
, seems there conflict jar dependencies.
to avoid problem, necessary to:
move or delete jboss jar files found in$jboss_home/lib/endorsed/
directory. copy jars bundled in initial .war file (the 1 of failed deploy) $jboss_home/lib/endorsed/
directory. jars bundled in .war file. that made it.
final notesi have confess find out real pain, , took me 4 days & running. made lot of troubleshooting jar dependencies, checking jboss logs, remote debugging, comparing java packages & classes versions, searching jars online , reading many articles jboss manuals, blogs, stackoverflow, javaranch, etc...
the soap client simple, deployment in jboss pretty problematic. solution not orthodox, since depends on jar files dependencies. i'm not sure if work everyone.
regards.
jboss5.x wsimport
Comments
Post a Comment