Petals SE Camel

Support deploy/init/start/stop/shutdown/undeploy hooks in Java Route definitions

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 0.5.1, 1.0.0
  • Fix Version/s: 0.5.2, 1.0.1
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    When an SU has lifecycle operations happening on it, we could notify the route implementation (a Camel RouteBuilder subclass) if specific actions need to be undertaken.

    For example, this makes sense if a Camel route relies on some configuration file: the start action on the lifecycle could be used reload this file without the need for undeploying the whole SU.

    We should thus call public methods named deploy/init/start/stop/shutdown/undeploy (without any parameters) on the Camel route implementation in the corresponding lifecycle actions.

    Show
    When an SU has lifecycle operations happening on it, we could notify the route implementation (a Camel RouteBuilder subclass) if specific actions need to be undertaken. For example, this makes sense if a Camel route relies on some configuration file: the start action on the lifecycle could be used reload this file without the need for undeploying the whole SU. We should thus call public methods named deploy/init/start/stop/shutdown/undeploy (without any parameters) on the Camel route implementation in the corresponding lifecycle actions.
  • Environment:
    -

People

Dates

  • Created:
    Tue, 9 Feb 2016 - 14:43:45 +0100
    Updated:
    Tue, 9 Feb 2016 - 15:28:47 +0100
    Resolved:
    Tue, 9 Feb 2016 - 15:28:47 +0100