Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • servicemix-eip-2009.01
    • 2013.02
    • servicemix-eip
    • None
    • Patch Available

    Description

      Currently the EIP Filter component does not send back exceptions (i.e. org.xml.sax.SAXParseException) as an error on the exchange which is the default behavior for other components (i.e. servicemix-saxon). As a result, there is no way to capture the message that generated the exception. We should change the implementation to propagate the exception up the call stack to allow the org.apache.servicemix.common.BaseLifeCycle.onMessageExchange() method to handle the exception and send it as an error on the exchange.

      Attachments

        1. SMXCOMP-568-3.3.18-fuse.diff
          5 kB
          Trevor Pounds
        2. SMXCOMP-568-SVN-r784248.diff
          5 kB
          Trevor Pounds

        Activity

          People

            Unassigned Unassigned
            tpounds Trevor Pounds
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated: