Hi Sergey,
I have replaced the CXFInterceptor with a ResponseHandler
implementation. So no chain-abort now. Body of the handleResponse is as
follows:
MultivaluedMap<String, Object> map = response.getMetadata();
map.add("Authentication-Info",
"nextnonce=\""+RestHandlerUtility.generateNonce(base_path)+"\"");
logger.debug("out message headers: " + map);
logger.info("response: " + response.getEntity());
As of this point, the entity still does not contain the Result tag
Again, my thanks.
Gabo
Gabo Manuel wrote:
Hi Sergey,
> Can you also do System.out.println(response.getEntity().toString())
in your mapper, before returning ?
2009-02-17 06:25:53,024 | INFO [l0-0][ SolegyFaultMapper]
entity: The server encountered some error. Involved personnel have
been notified of this incident. Please contact support for follow-up.
Issue #2009480001
TCPMon captured:
HTTP/1.1 500 Internal Server Error
Content-Type: text/plain
Authentication-Info:
nextnonce="MTIzNDg1MTk1MzAzOTphYjk1ZDllOTkzMDEyNWRlZThkY2ExOWExZThjNjYwNQ=="
Content-Type: text/plain
Content-Length: 163
Server: Jetty(6.1.11)
<Result>The server encountered some error. Involved personnel have
been notified of this incident. Please contact support for follow-up.
Issue #2009480001</Result>
> I'm bewildered :-) I've no idea where this <Result> is coming
from...I've searched the CXF code base for expressions
> containing 'Result' and found no obvious culprit...
I'm thinking maybe it is translated as a regular bean and that the
said class is annotated as such? I tried debugging the
OutputStream os = outMessage.getContent(OutputStream.class); step by
step to no avail.
Gabo
