"Could not send message" normally means that the service isn't working. Are you able to bring up the service WSDL from a browser? If not, I would not worry about the SOAP client until you can get that visible.
My JUnit test entry has an example of how to use embedded Tomcat: http://www.jroller.com/gmazza/entry/writing_junit_test_cases_for#testtc And, of course, my WSDL-first example has more information on deploying to Tomcat: http://www.jroller.com/gmazza/entry/creating_a_wsdl_first_web1 (See Notes at the bottom, step #3 for URLs to obtain the WSDL) HTH, Glen ericomtx wrote: > > I´m trying to run the java_first_jaxws sample that comes with apache cxf > 2.1.3 > > I would like to run this sample with TomCat and not with Jetty > > I can register my Server in TomCat but when I run the Client Class I get > the following exception: > > INFO: Interceptor has thrown exception, unwinding now > org.apache.cxf.interceptor.Fault: Could not send Message. > at > org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64) > > .... > > Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Could not > send Message. > at > org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:145) > at $Proxy41.sayHi(Unknown Source) > at demo.hw.client.Client.main(Client.java:53) > Caused by: org.apache.cxf.interceptor.Fault: Could not send Message. > > The only modification that I made in the source code was to change the > Jetty 9000 port to TomCat 8080 > > Best Regards > > > > -- View this message in context: http://www.nabble.com/java_first_jaxws-sample-in-TomCat-tp20193771p20199762.html Sent from the cxf-user mailing list archive at Nabble.com.
