Uploaded image for project: 'FUSE Mediation Router'
  1. FUSE Mediation Router
  2. MR-370

onException specified after route statements does not work

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Minor
    • 2.4.0-fuse-02-00, 2.5.0-fuse-00-00
    • 2.4.0-fuse-01-00
    • None
    • None

    Description

      If you put onException AFTER the route definition, the build compiles with no problem, but the exception does get triggered. The work-around for now is to make sure that all onExceptions are specified PRIOR to route definition. This should be fixed to allow for onException after the routes or at least throw some sort of error saying that this is not allowed - not sure which solution is best yet.

      Attachments

        Issue Links

          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) MR-382 onException should not be possible to specify after routes

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              cibsen@redhat.com Claus Ibsen
              janstey@redhat.com Jonathan Anstey
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: