Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-4189

Exception by None address in ReplyTo header for request-response MEP

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.5.3, 2.6
    • Component/s: None
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      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.

        Attachments

        1. Addressing.patch
          7 kB
          Andrei Shakirin

          Activity

            People

            • Assignee:
              dkulp Daniel Kulp
              Reporter:
              ashakirin Andrei Shakirin
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: