; BTW all this is the side effect of:
> https://bugs.openjdk.java.net/browse/JDK-6695379
>
> Babak
>
> andrewcelerity wrote
> I opened a Jira ticket and attached a sample app that replicates
> the problem. Hopefully it'
I opened a Jira ticket and attached a sample app that replicates the problem.
Hopefully it's an easy fix.
https://issues.apache.org/jira/browse/CAMEL-8160
--
View this message in context:
http://camel.465427.n5.nabble.com/Changes-in-Java-8-generics-breaking-Camel-tp5760638p5760876.html
Sent
I am using Camel 2.14.0.
I do see one problem, though maybe it's just a lack of understanding of the
process you're using to compare results. Annotations like @Consume have a
retention policy of runtime, meaning the compiler leaves them in the
compiled class file (I believe). Your decompiled cod
Java 8 made a changes to generics that is currently not allowing camel to
start up, and if it did start up would be in a bad state. Bridge methods
now get a copy of the annotations placed on the real method. This is bad
when combined with Camel annotations. For example:
interface Something {
