[GitHub] camel pull request #1167: CAMEL-10308

Github user tivv closed the pull request at: https://github.com/apache/camel/pull/1167 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Adding type awareness in Camel route

Hi Claus, Thanks for the reply. Sure that's fine, I agree 3.0 would be better to be targeted than 2.x as this introduces some schema updates. Including this one, I'm always looking for the chance to make any contribution to Camel. If there's anything I can help please let me know. Thanks,

Re: Camel 2.19 or 3.0 : lookup endpoint by custom id

Ah great, thx Claus On Saturday, 17 September 2016, Claus Ibsen wrote: > 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 > wrote: > > Hi > > > >

Re: Camel 2.19 or 3.0 : lookup endpoint by custom id

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 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

Re: Adding type awareness in Camel route

Hey Can we take this discussion post Camel 2.18 release. We are working on the last details to get it ready, and its our main focus to get this new release out. After this release we will pickup talks about the next releases whether that is 2.19 or 3.0, and for the latter what the broad goals

Re: Camel 2.19 or 3.0 : lookup endpoint by custom id

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

Camel 2.19 or 3.0 : lookup endpoint by custom id

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