[jboss-user] [JBossWS] - Re: Consuming .net Web Service using JBOSSWS
Ok. I tried with a different service and I am getting the same error. Could somebody
please help?
Service is located at
http://www.xmlme.com/WSAmazonBox.asmx?WSDL
Here is the client code:
| URL wsdlURL = new URL("http://www.xmlme.com/WSAmazonBox.asmx?WSDL");
| ServiceFactoryImpl servFactory = new ServiceFactoryImpl();
| URL mappingURL = new File("jaxrpc-mapping.xml").toURL();
| QName qname = new QName("http://xmlme.com/WebServices";,
"AmazonBox");
| ServiceImpl service = (ServiceImpl)servFactory.createService(wsdlURL, qname,
mappingURL);
| Call call = service.createCall();
| call.setOperationName(new QName("http://xmlme.com/WebServices";,
"DvdBox"));
| call.setProperty(Call.SOAPACTION_USE_PROPERTY, Boolean.TRUE);
| call.setProperty(Call.SOAPACTION_URI_PROPERTY,
"http://xmlme.com/WebServices/DvdBox");
| call.setTargetEndpointAddress("http://www.xmlme.com/WSAmazonBox.asmx...;
| DvdBox req = new DvdBox("Disney");
| Object response = call.invoke(new Object[] {req});
| if(response instanceof DvdBoxResponse) {
| DvdBoxResponse result = (DvdBoxResponse)response;
| System.out.println("Finished" + result.getDvdBoxResult());
| }
|
Here is the exception stack trace I am getting:
| javax.xml.rpc.JAXRPCException: Cannot obtain operation meta data for:
{http://xmlme.com/WebServices}DvdBox
| at org.jboss.ws.jaxrpc.CallImpl.getOperationMetaData(CallImpl.java:840)
| at org.jboss.ws.jaxrpc.CallImpl.getOperationMetaData(CallImpl.java:820)
| at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:618)
| at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:404)
| at xmlme.client.Test.call(Test.java:50)
| at xmlme.client.Test.main(Test.java:21)
|
I have generated the required artifacts from wstools. Set the proxy server settings on the
command line.
What I am doing wrong??
Any help is appreciated.
Thanks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973557#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...