camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <>
Subject [jira] [Commented] (CAMEL-6404) cCXF route proxy cannot return Fault message to client when Dataformat is CXF_MESSAGE
Date Fri, 31 May 2013 14:21:27 GMT


Willem Jiang commented on CAMEL-6404:

I just checked the code, the NPE is caused by the DefaultCxfBinding try to find the processed
object from CXF message. As the CXF_MESSAGE consume the input stream and throw out the exception,
the DefaultCxfBing get the NPE. 
This issue can be fixed by letting DefaultCxfBinding ignore the CXF message content when there
is nothing. camel-cxf will take care of the fault message (which is turned into an exception)
> cCXF route proxy cannot return Fault message to client when Dataformat is CXF_MESSAGE
> -------------------------------------------------------------------------------------
>                 Key: CAMEL-6404
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-cxf
>            Reporter: Meifang Shen
>         Attachments:
> use CXF component with CXF_MESSAGE dataFormat to call any service, and the response of
this service is a fault, then you can see this exception.
> {noformat} 
> Exception in thread "default-workqueue-1" java.lang.NullPointerException
> 	at org.apache.camel.component.cxf.DefaultCxfBinding.getContentFromCxf(
> 	at org.apache.camel.component.cxf.DefaultCxfBinding.populateExchangeFromCxfResponse(
> 	at org.apache.camel.component.cxf.CxfClientCallback.handleException(
> 	at org.apache.cxf.interceptor.ClientOutFaultObserver.onMessage(
> 	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream$
> 	at org.apache.cxf.workqueue.AutomaticWorkQueueImpl$
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
> 	at java.util.concurrent.ThreadPoolExecutor$
> 	at org.apache.cxf.workqueue.AutomaticWorkQueueImpl$AWQThreadFactory$
> 	at
> {noformat} 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message