camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-8491) Camel POJO producer/consumer should defer starting until CamelContext is starting
Date Mon, 16 Mar 2015 11:59:38 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-8491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-8491.
--------------------------------
    Resolution: Fixed

> Camel POJO producer/consumer should defer starting until CamelContext is starting
> ---------------------------------------------------------------------------------
>
>                 Key: CAMEL-8491
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8491
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core, eip
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.16.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message