Hi I have said this many times. We love contributions http://camel.apache.org/contributing.html
Surely it would be great if people who have need for and use CDI a lot would dig in and help fix/improve/maintain the camel-cdi component. And surely helping with documentation and examples is also much welcome. On Mon, Sep 16, 2013 at 10:06 PM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Basically when i looked the only useful stuff was the registry to reuse cdi > beans. > > Doing an @ExchangeScoped was not easy since threading is not well handled > by camel. > > Finally using camel injections in cdi beans was interesting to trigger > routes. > > Creating a route from annotations is not that efficient IMO. > > For memories here is a part if my tests: > https://github.com/rmannibucau/camel-cdi-extension/blob/master/README.md > Le 16 sept. 2013 21:54, "Charles Moulliard" <ch0...@gmail.com> a écrit : > >> I'm busy for 3 days (training / workshops) but will have a look this friday >> and update what we have done. >> >> >> On Mon, Sep 16, 2013 at 9:49 PM, John D. Ament <john.d.am...@gmail.com >> >wrote: >> >> > I've actually been curious about this as well. Some of the things >> > I"ve thought about that would be cool: >> > >> > - Firing CDI events for exchanges, and making processors simply >> > observer methods. >> > - Using proper CDI scopes (rather than being bound to the spring >> contexts) >> > >> > On Mon, Sep 16, 2013 at 11:12 AM, Harald Wellmann >> > <hwellmann...@gmail.com> wrote: >> > > Going by its documentation camel-cdi looks rather incomplete and >> > > broken to me. Is this component a prototype or ready for production? >> > > >> > > There does not seem to be any documentation other than >> > > http://camel.apache.org/cdi.html >> > > >> > > which contains many broken links to Java classes or Javadoc pages. >> > > >> > > Injecting a CdiCamelContext and configuring and starting it in a >> > > @Singleton @Startup @PostConstruct method does not make sense to me, >> > > given that the CdiCamelContext already starts itself in its own >> > > @PostConstruct method. >> > > >> > > Is there a way to configure a context before starting it? >> > > >> > > How do you work with more than one Camel context in one CDI >> application? >> > > >> > > Best regards, >> > > Harald >> > >> >> >> >> -- >> Charles Moulliard >> Apache Committer / Architect @RedHat >> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com >> -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
