Camel-Cdi not injecting CamelContext with Registery

Question

I am using camel-cdi and it is injecting the CamelContext, detecting all the routes in project. But I want a CamelContext with a registry because I have some components that I use in camel routes like shown below.

    SimpleRegistry registry = new SimpleRegistry();
    registry.put("actionProcessor", actionProcessor);
    registry.put("jpa", jpaComponent);
    registry.put("jtaTransactionManager", platformTransactionManager);

    CamelContext camelContext = new DefaultCamelContext(registry);

When I inject CamelContext the components like actionProcess, jpa are not recognized. when in my Route I have

    .to("bean:actionProcessor?method=myMethod(${body})")

but my bean does not get executed. I documentation I read use # before components name which are in registry but still it is not working.

Please suggest how can I achieve this using camel-cdi.

Answer 1

We have been using this for years without any problem

public class ContextFactory {

    @Produces
    @ApplicationScoped
    @ContextName("Demo")  
    static final CamelContext createContext() {
        CdiCamelContext context = new CdiCamelContext();                
        context.setStreamCaching(true);                
        context.disableJMX();       
        return context;
    }

}   


@ContextName("Demo")
public class MyRouteBuilder extends RouteBuilder {

    from("...")
    .to("bean:actionProcessor?method=myMethod")
}


@Named("actionProcessor")
public class MyActionProcessor{

    public void myMethod(@Body String body) {}
}

Of course, in order to work, you need to activate the JEE bean discovery (=add a "beans.xml" file in META-INF or WEB-INF) !

Answer 2

Did you already try with creating a CdiCamelContext (a subclass of DefaultCamelContext) ?

Otherwise, a more elegant would be to annotate your various classes, eg:

@Named("actionProcessor")
public class MyActionProcessor{
...
}