I managed to find the JIRA ticket https://issues.apache.org/jira/browse/CAMEL-7778
On Sat, Sep 17, 2016 at 11:31 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > Yeah we have a JIRA ticket about this, so the Camel endpoint reigistry > has an id as well. > Currently only the url is registered. > > Endpoints in Camel don't really have the notion of an id, only url. > > Its when you use Spring or Blueprint etc then they have an endpoint > factory that create endpoints and have an id associated to the factory > of the bean it creates. And then when you lookup an endpoint by an id, > you lookup in their registries and they find that bean instance. > > CDI has @Qualified and Spring has @Named to associate an id with the > bean when not using XML. > > Its more tricky to implement as those ids, can be harder to get hold > of in those factories AFAIR. > > But the JIRA ticket was about introducing the id natively on endpoint > and endpoint registry. I think this kind of change is better for Camel > 3.0. > > > > On Sat, Sep 17, 2016 at 11:03 AM, Luca Burgazzoli <lburgazz...@gmail.com> > wrote: >> Hello everyone, >> >> I'm wondering if it could make sense to register enpoints in context's >> registry having an option so set theirs id; >> >> The aim is to have a common way to identify an endpoint other by uri, so >> that: >> - @Produce(ref = "myEndpontId") would work the same way in any context >> - People willing to integrate with camel using a producer template do >> not need to know the whole uri, i.e. in vertx-camel-bridge mapping >> between a vertx address and an endpoint could be done by id. >> >> >> I could elaborate it a little bit more if you think it could make sense. >> >> >> Best regards, >> Luca >> >> >> --- >> Luca Burgazzoli > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
