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
