Re: Changes in Java 8 generics breaking Camel

2014-12-22 Thread andrewcelerity
If you reply to this email, your message will be added to the discussion below: http://camel.465427.n5.nabble.com/Changes-in-Java-8-generics-breaking-Camel-tp5760638p5760975.html To unsubscribe from Changes in Java 8 generics breaking Camel, click here http://camel.465427.n5

Re: Changes in Java 8 generics breaking Camel

2014-12-22 Thread Babak Vahdat
message will be added to the discussion below: http://camel.465427.n5.nabble.com/Changes-in-Java-8-generics-breaking-Cam el-tp5760638p5760975.html To unsubscribe from Changes in Java 8 generics breaking Camel, click here http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubsc

Re: Changes in Java 8 generics breaking Camel

2014-12-18 Thread andrewcelerity
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

Re: Changes in Java 8 generics breaking Camel

2014-12-15 Thread andrewcelerity
code does not show any annotations. I fully expect to see the same methods generated via Java 7 and 8, but the annotations on them should be different in the 8 generated byte code. -- View this message in context: http://camel.465427.n5.nabble.com/Changes-in-Java-8-generics-breaking-Camel

Re: Changes in Java 8 generics breaking Camel

2014-12-15 Thread Willem Jiang
in the 8 generated byte code. -- View this message in context: http://camel.465427.n5.nabble.com/Changes-in-Java-8-generics-breaking-Camel-tp5760638p5760703.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Changes in Java 8 generics breaking Camel

2014-12-15 Thread Babak Vahdat
Am 15.12.14 14:38 schrieb andrewcelerity unter and...@celerityglobal.com: 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

Changes in Java 8 generics breaking Camel

2014-12-12 Thread andrewcelerity
. BeanInfo.isValidMethod does not allow for bridge methods 2. There are now 2 methods listening to the same endpoint Is this a bug that should be reported? Any ideas on a workaround? I'm about to downgrade to java 7. -- View this message in context: http://camel.465427.n5.nabble.com/Changes-in-Java-8-generics

Re: Changes in Java 8 generics breaking Camel

2014-12-12 Thread Babak Vahdat
Am 12.12.14 16:48 schrieb andrewcelerity unter and...@celerityglobal.com: 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