Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-8491

Camel POJO producer/consumer should defer starting until CamelContext is starting

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.16.0
    • Component/s: camel-core, eip
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      See SO
      http://stackoverflow.com/questions/29031456/why-does-this-apache-camel-intercept-not-work

      When using @Produce @Consume and other POJO injected resources they may be started during the injection phase.

      We should defer starting till CamelContext has started other resources, and its routes, so they are ready before the POJO resources.

      For example this allows interceptors and whatnot to be properly initialized at first.

      So we should have some api on CamelContext these POJO resources can register and then let CamelContext handle their lifecycle.

      This also aids to ensure these resources gets shutdown when CamelContext shutdown itself also.

        Attachments

          Activity

            People

            • Assignee:
              davsclaus Claus Ibsen
              Reporter:
              davsclaus Claus Ibsen
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: