e.org/cdi.html
It's possible I'm misunderstanding this somehow and that the deprecation is
due to a difference in Camel and the later versions of Karaf? Or does this
have to do with Guillaume's new PAX DS implementation of CDI?
Thanks for any clarification.
Ranx
I'm not sure what the state of thought about Camel 3 is or where it is in its
development cycle or even if this is the correct place to post this but I've
thought about it some lately. There are a number of reasons I think Java 8
would be great for the next generation of Camel which I won't go into
Is this the wrong place for such discussions?
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-3-tp5777217p5777295.html
Sent from the Camel Development mailing list archive at Nabble.com.
Is there a discussion group or list or issue where Camel 3 features are being
discussed? I've found this:
http://camel.apache.org/camel-30-ideas.html
I'd upvote the baseline of JDK 8. By the time 3.0 becomes hardened it would
be a realistic baseline and it provides too many mechanisms for strea
I'd like to amplify one of the comments by Claus about slimming the core of
camel and making other components less dependent on it.
I'd like to see the core limited to compile time dependencies - annotations,
interfaces and factories only. The runtime engine might be blueprint,
spring, or whateve
This past week I ran into a bug that I found almost inadvertently. Using a
package scan for route builders the karaf instance fired up and "found" my
service. Unfortunately what it did was loaded a class that was private to
another bundle. Obviously I had something misconfigured as it didn't fin
<
ml-node+s465427n5776560...@n5.nabble.com> wrote:
> Hi
>
> Use Camel 2.16 onwards
> http://camel.apache.org/using-camelproxy.html
>
> On Fri, Jan 22, 2016 at 4:51 PM, Ranx <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=5776560&i=0>> wrote:
>
&
2.15.1.redhat-620133
On Fri, Jan 22, 2016 at 1:18 AM, Claus Ibsen-2 [via Camel] <
ml-node+s465427n577650...@n5.nabble.com> wrote:
> What version of Camel do you use?
>
> On Thu, Jan 21, 2016 at 9:18 PM, Ranx <[hidden email]
> <http:///user/SendEmail.jtp?type=node&
I've been working with the @Produce annotation as it allows me to carve the
routes into nice stages and let's me do CamelBlueprintTestSupport and route
substitution for testing and mutliple camel contexts aren't a problem. It
works well except for one annoying bug.
If I define an interface of:
p
