camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5553) support injection of Endpoint and @Produce @Consume annotations
Date Mon, 03 Sep 2012 14:47:07 GMT


james strachan commented on CAMEL-5553:

You can now use a more CDI-like injection of Endpoints or ProducerTemplate via:
public class Foo {
    @Inject @Uri("mock:foo") Endpoint endpoint;

    @Inject @Uri("seda:bar") ProducerTemplate producer;

> support injection of Endpoint and @Produce @Consume annotations
> ---------------------------------------------------------------
>                 Key: CAMEL-5553
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-cdi
>            Reporter: james strachan
> we don't yet support the various camel annotation injections in CDI yet; we should support
the same capabilities as we have in spring/guice
> I guess a more CDI way to do endpoint injection might be to have an annotation for endpointURI
specification. Then you'd either use 
> {code}
> public class MyBean { 
>   // named reference injection
>   @Inject @Named("foo") Endpoint bar;
>   // URI based injection
>   @Inject @Uri("mock:whatnot") MockEndpoint foo;
> ...
> }
> {code}
> Rather than using the DI-agnostic @EndpointInject annotation - though I guess we could
support it too (though having Inject twice looks a bit icky and not as DRY)...
> {code}
> public class MyBean { 
>   // using current annotation...
>   @Inject @EndpointInject(uri = "mock:whatnot") MockEndpoint bar;
> ...
> }
> {code}
> For handling @Consume it would be nice to avoid having to use @Inject too as that seems
a bit odd (since there's no injection going on).
> For @Produce I guess we could support a straight @Inject of a ProcessorTemplate; allowing
use of @Uri annotation to specify the default URI to send to

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message