[JBoss Web Services Metro] - JBossMetro Client- Unable to access WS deployed at remote se
by mtirumalreddy
Hi,
I got one more problem while using Metro client for a remote webservice. I have one WS, which is deployed at our local server and i am able to connect it by mentioning full location of the WSDL (http://localhost:8080/SampleService/Sample.wsdl).
But in second scenario, i am trying to connect a WS, which is developed in different technology and deployed in remote location. We got the endpoint address something like this.
anonymous wrote : http://hostname:portnumber/
I created client using wsconsume tool and created jar to connect the webservice. iam getting the following exception:
anonymous wrote :
| Exception in thread "main" com.sun.xml.internal.ws.streaming.XMLStreamReaderException: XML reader error: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,62]
| Message: White spaces are required between publicId and systemId.
| at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.wrapException(XMLStreamReaderUtil.java:242)
| at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:70)
| at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.nextContent(XMLStreamReaderUtil.java:85)
| at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.nextElementContent(XMLStreamReaderUtil.java:75)
| at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.hasWSDLDefinitions(RuntimeWSDLParser.java:195)
| at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:108)
| at com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:226)
| at com.sun.xml.internal.ws.client.WSServiceDelegate.(WSServiceDelegate.java:189)
| at com.sun.xml.internal.ws.client.WSServiceDelegate.(WSServiceDelegate.java:159)
| at com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:83)
| at javax.xml.ws.Service.(Service.java:56)
| at v1.ase.aorta.cqs_co_za.AseService.(AseService.java:45)
| at v1.ase.aorta.cqs_co_za.client.TestAseService.main(TestAseService.java:11)
| Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,62]
| Message: White spaces are required between publicId and systemId.
| at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:588)
| at com.sun.xml.internal.ws.util.xml.XMLStreamReaderFilter.next(XMLStreamReaderFilter.java:78)
| at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:51)
| ... 11 more
|
I changed some namespaces and i got different exception saying that the service location is un parsable. But if i use, AXIS2 for the same, iam able to connect the service eventhough i didnot mentioned the full url of the WSDL.
If any one got any solution for this, please let me know.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251845#4251845
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251845
14 years, 8 months
[JBossWS-Metro] - JBoss & METRO Classpath issues on Linux?
by bmsantos
Hi all,
Recently I got another unexpected error out of the JBoss/METRO deployment. While running the web services client under Linux I got the following error:
javax.xml.ws.WebServiceException: Unable to load Provider: Failed to load javax.xml.ws.spi.Provider: org.jboss.ws.core.jaxws.spi.ProviderImpl
javax.xml.ws.WebServiceException: Unable to load Provider: Failed to load javax.xml.ws.spi.Provider: org.jboss.ws.core.jaxws.spi.ProviderImpl
at javax.xml.ws.spi.Provider.provider(Provider.java:90)
at javax.xml.ws.Service.(Service.java:81)
...
The web services have been working just fine under windows and in one other Linux machine. I was able to overcome the problem by removing the jboss-jaxws.jar from the JBOSS_HOME/server/name/lib directory.
As we still have a few other Linux boxes to go through and because we've not run enough testing on it after the removal of this jar, my question is... is this a required jar when working under the METRO stack? If so, what's the impact of not having it in the classpath.
We are using JBoss 4.2.3 GA + METRO 3.1.1 stack.
P.S. When first installed we've also noticed that we had to remove the jboss-saaj.jar lib from the classpath since the METRO install did not clean it.
Thanks,
B.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250479#4250479
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250479
14 years, 8 months