You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andrei Shakirin (Created) (JIRA)" <ji...@apache.org> on 2012/03/21 14:29:39 UTC
[jira] [Created] (CXF-4189) Exception by None address in ReplyTo
header for request-response MEP
Exception by None address in ReplyTo header for request-response MEP
--------------------------------------------------------------------
Key: CXF-4189
URL: https://issues.apache.org/jira/browse/CXF-4189
Project: CXF
Issue Type: Improvement
Reporter: Andrei Shakirin
Priority: Minor
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" property.
Patch is attached.
Regards,
Andrei.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4189) Exception by None address in ReplyTo
header for request-response MEP
Posted by "Andrei Shakirin (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Shakirin updated CXF-4189:
---------------------------------
Attachment: Addressing.patch
> Exception by None address in ReplyTo header for request-response MEP
> --------------------------------------------------------------------
>
> Key: CXF-4189
> URL: https://issues.apache.org/jira/browse/CXF-4189
> Project: CXF
> Issue Type: Improvement
> Reporter: Andrei Shakirin
> Priority: Minor
> 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" property.
> Patch is attached.
> Regards,
> Andrei.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4189) Exception by None address in ReplyTo
header for request-response MEP
Posted by "Daniel Kulp (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-4189.
------------------------------
Resolution: Fixed
Fix Version/s: 2.6
2.5.3
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: https://issues.apache.org/jira/browse/CXF-4189
> 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" property.
> Patch is attached.
> Regards,
> Andrei.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira