Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-10434

camel-cxf - failure processor for custom exception handling cannot get the original message

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: fuse-7.2
    • Fix Version/s: fuse-7.4-GA
    • Component/s: Camel, Fuse EAP
    • Labels:

      Description

      As described in [1]:

      "I configured custom exception handling for a CXF consumer where I want to use my own processor.

      Lile this:

      onException(Exception.class)
      .handled(false)
      .useOriginalMessage()
      .process(failureResponseProcessor);

      or:

      <onException useOriginalMessage="true">
      <exception>java.lang.Exception</exception>
      <handled><constant>false</constant></handled>
      <process ref="failureResponseProcessor"/>
      </onException>

      If allowStreaming is enabled on the CXF consumer endpoint, my FailureResponseProcessor cannot get the original body (the body part of CachedCxfPayload seems to be empty).

      If I set allowStreaming to false, the processor works as expected."

      Claus suggested stream-caching, but the user reports it does not help.

      [1] https://issues.apache.org/jira/browse/CAMEL-13376

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                ffang Freeman(Yue) Fang
                Reporter:
                rick_wagner Rick Wagner
                Tester:
                Viliam Kasala
                Involved:
                Rick Wagner
              • Votes:
                1 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: