It can be anything, for example some server-side error not related to
the web service provider itself; for example if you're hosting the web
service on Jetty and Jetty is having a startup problem ("can't read
config file") that might trigger an HTML response.
I'm not certain that's your problem though because typically CXF will
report back part of the HTML error message if that is what is
happening. It could also be some XML formatting error or wrong XML
library being used.
This blog entry is somewhat dated but you may also wish to try embedded
Tomcat testing:
http://www.jroller.com/gmazza/entry/junit_web_service_testing if the
results from Wireshark are inconclusive, to see if/what it reports
differently.
Glen
On 02/14/2012 05:40 AM, Stephane Eybert wrote:
Hi Glen,
Thanks for the tip. I'm now running wireshark. I can see some traffic when
running the integration tests.
Now I'll dig in the doc to see how I can see the actual content passing by.
Other than that, would you have an idea about what could trigger an html
response in my CXF web service ?
Kind Regards,
Stephane
--
View this message in context:
http://cxf.547215.n5.nabble.com/com-ctc-wstx-exc-WstxEOFException-Unexpected-EOF-in-prolog-when-run-in-integration-test-on-jetty-tp5478597p5482075.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza
