Hi Henrik
For some reasons I can only see your message in Archives, but not Nabble. >>The handleResponse() method in >>my filter gets called, but I've found that if I return any kind of >>error, i.e. a category 400 or 500 type error, the XML that I'm returning >>as the content doesn't get rendered in the browser If one returns a custom Response from a filter, then its entity, if any, will be serialized by the available writers. So if you set a String instance as a custom entity and you happen to have a custom message body writer which can wrap Strings then the browser would show it as a plain text sequence. Starting from CXF 2.2.4 it is possible to indicate that writers have to be ignored. In meantime, the best way would be to return an object like ExceptionInfo which will be serialized by the appropriate XML writer. Is it what might be happening in your case ? If you're thinking of doing JAXRS only then filters should do well. Cheers, Sergey
