sure the problem could be reproduce with project at this github
https://github.com/wangyan100/springboot-camel-esb

---------- Forwarded message ---------
From: lburgazzoli [via Camel] <ml+s465427n5824740...@n5.nabble.com>
Date: Mon, Oct 15, 2018 at 7:59 AM
Subject: Re: o.a.c.i.DefaultCamelBeanPostProcessor : No CamelContext
defined yet so cannot inject into bean:
To: nono <wyan...@gmail.com>


Hello,

can you open a new issue with a reproducer ? There may be more
condition that lead to such warning.

---
Luca Burgazzoli

On Sun, Oct 14, 2018 at 5:11 PM Zoran Regvart <[hidden email]
<http:///user/SendEmail.jtp?type=node&node=5824740&i=0>> wrote:

>
> Hello,
> the versions are listed in the issue[1], until we release if you need
> this fix the only way you can get it is if you use the snapshot
> versions.
>
> Mixing two different versions of Camel will probably lead to more issues.
>
> zoran
>
> On Fri, Oct 12, 2018 at 1:14 PM, Wang Yan <[hidden email]
<http:///user/SendEmail.jtp?type=node&node=5824740&i=1>> wrote:
> > Could you please suggest which release could fix this problem? i dont
want
> > to use snapshot version.
>
> [1] https://issues.apache.org/jira/browse/CAMEL-12087
> --
> Zoran Regvart


------------------------------
If you reply to this email, your message will be added to the discussion
below:
http://camel.465427.n5.nabble.com/o-a-c-i-DefaultCamelBeanPostProcessor-No-CamelContext-defined-yet-so-cannot-inject-into-bean-tp5824553p5824740.html
To unsubscribe from o.a.c.i.DefaultCamelBeanPostProcessor : No CamelContext
defined yet so cannot inject into bean:, click here
<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5824553&code=d3lhbmJveEBnbWFpbC5jb218NTgyNDU1M3wxMTU1MzAzODM=>
.
NAML
<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>

Reply via email to