cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (CXF-4189) Exception by None address in ReplyTo header for request-response MEP
Date Fri, 23 Mar 2012 17:33:28 GMT


Daniel Kulp resolved CXF-4189.

       Resolution: Fixed
    Fix Version/s: 2.6
         Assignee: Daniel Kulp

Patch applied, but I did have to make some modifications as we had a bunch of systest failures
with just your changes.

> Exception by None address in ReplyTo header for request-response MEP
> --------------------------------------------------------------------
>                 Key: CXF-4189
>                 URL:
>             Project: CXF
>          Issue Type: Improvement
>            Reporter: Andrei Shakirin
>            Assignee: Daniel Kulp
>            Priority: Minor
>             Fix For: 2.5.3, 2.6
>         Attachments: Addressing.patch
> Hi,
> MAPAggregator throws exception if service receives message containing None address in
ReplyTo header for request-response MEP.
> Basically it is correct, but unfortunatelly doesn't work with dynamic services.
> Dynamic CXF service implementing Provider<T> interface interprets all incoming
messages as having request-response MEP. Precisely  saying, there is not reliable method to
recognize OneWay and request-response MEPs on inbound chain for dynamic service: invoke()
return value is not known yet, there is no service model available and it is not always possible
to detect it from message.
> As result dynamic CXF service throws exception by receiveing oneWay message with None
address in ReplyTo.
> Proposal: display a warning for service inbound chain and throw exception only for outbound
chain, where dynamic service indicates oneWay operation via returned value and "jaxws.provider.interpretNullAsOneway"
> Patch is attached.
> Regards,
> Andrei.

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


View raw message