Could you send me the full debug log when you try to access
http://localhost:8192/EchoService/main.wsdl from your browser?
Freeman
angeloNZ wrote:
I wasn't getting any sort of exception when deploying the SA with the
consumer and provider servicename the same. I've now tried changing the
name of the consumer service and still get the unable to find the requested
resource problem.
I can get the external web service's wsdl to show up in the browser by doing
http://localhost/MockWebService/services/EchoService?wsdl
and I can make requests to it's methods when using a soapUI client as well.
So I'm not really sure what else to look for.
Here's what I get from turning on DEBUG whenever I try to access
.../EchoService/main.wsdl
DEBUG - jetty - chain=null
DEBUG - jetty - servlet holder=jbiServlet
DEBUG - jetty - RESPONSE /EchoService/main.wsdl
404
DEBUG - jetty - REQUEST /EchoService/main.wsdl on
org.mortbay.jetty.HttpC
onnect...@1b6c74
DEBUG - jetty - servlet=jbiServlet
DEBUG - jetty - chain=null
DEBUG - jetty - servlet holder=jbiServlet
DEBUG - jetty - RESPONSE /EchoService/main.wsdl
404
Freeman Fang wrote:
Hi,
Are you sure your SA get deployed successfully? I notice your http
consumer and provider has same servicename which should cause conflict
when deploy your SA.
Could see any exception from servicemix console when you deploy the SA?
Also, you use
wsdlResource="http://localhost/MockWebService/services/EchoService?wsdl";
to refer the wsdl, which means the service already exposed from
http://localhost/MockWebService/services/EchoService
Could you access the
http://localhost/MockWebService/services/EchoService?wsdl from your web
browser?
Freeman
angeloNZ wrote:
thanks for your reply Freeman.
however, using http://localhost:8192/EchoService/main.wsdl gives me the
same
resource not found problem.
