cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aki Yoshida (JIRA)" <>
Subject [jira] [Commented] (CXF-4248) DocLiteralInInterceptor throws NPE if oneWay operation sends non-empty response
Date Thu, 13 Dec 2012 13:18:16 GMT


Aki Yoshida commented on CXF-4248:

I noticed that the constant is incorrectly spelled (REPONSE). (okay, it's a valid french word,
but that doesn't fit to the other constants.)

so i mark this constant as deprecated and add the correctly spelled one (RESPONSE).

> DocLiteralInInterceptor throws NPE if oneWay operation sends non-empty response
> -------------------------------------------------------------------------------
>                 Key: CXF-4248
>                 URL:
>             Project: CXF
>          Issue Type: Improvement
>            Reporter: Andrei Shakirin
>            Assignee: Aki Yoshida
>            Priority: Minor
>             Fix For: 2.4.8, 2.5.4, 2.6.1
>         Attachments: HTTPConduit.patch, OneWayResponseProcessing-fixed.patch, OneWayResponseProcessing.patch
> Hi,
> Test case: Web service provides oneWay operation (SoapUI mock), but sends non-empty SOAP
response back
> Expected: response will be ignored
> Actual: DocLiteralInInterceptor throws NPE
> Caused by: java.lang.NullPointerException
>         at org.apache.cxf.interceptor.DocLiteralInInterceptor.shouldWrapParameters(
>         at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(
>         at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
>         at org.apache.cxf.endpoint.ClientImpl.onMessage(
>         at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(
>         at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(
>         at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(
>         at org.apache.cxf.transport.AbstractConduit.close(
>         at org.apache.cxf.transport.http.HTTPConduit.close(
>         at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSende
> Fix proposal: I have discovered (thanks Aki!) that there are some cases when oneWay response
can be proceeded. Regarding Basic Profile 1.1: 
> R2714 For one-way operations, an HTTP Response MESSAGE MAY contain an envelope.
> One-way operations typically do not produce SOAP responses. However, some INSTANCEs may
choose to communicate infrastructure-related faults (e.g. MustUnderstand, VersionMismatch)
in the HTTP Response message.
> In addition to this, the use of some protocol extensions (e.g.
> WS-ReliableMessaging) may create the possibility for non-empty responses to one-way messages.
For these reasons the Basic Profile 1.1 requirement that the HTTP Response message not contain
a SOAP envelope has been relaxed.
> I would propose to process successful oneWay responses only in following cases:
> A) if RM is active (check RMMessageConstants.RM_PROPERTIES_OUTBOUND, RMMessageConstants.RM_PROPERTIES_INBOUND)
> B) if user activate it with org.apache.cxf.transport.processOneWayResponse property on
> In other case oneWay response will be ignored by client.
> Patch is attached.
> Regards,
> Andrei.

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