Just a note, you can remove more than one header at once with <removeHeaders pattern="Camel*"/> or even <removeHeaders pattern="*"/>
Using wildcards and such. I don't think the headers that are populated off of the jetty endpoint are going to be causing the issue. If you are just trying to pass along the JSON string straight through to the CXF producer that is mapped to your webservice you wouldn't need to do any unmarsheling along the way. Given that the error returned is a 404, have you used SOAP UI or some other utility to hit the service directly to ensure messages can go through from the box you are running servicemix on? Seems that a webserver might be listening, but that the path is not correct. It may be that the operation name in your instance is not recognized as a URL path. -- View this message in context: http://camel.465427.n5.nabble.com/HOW-TO-Jetty-JSON-and-Restful-Services-tp5713702p5713711.html Sent from the Camel - Users mailing list archive at Nabble.com.
