And no Camel 2.14.x is EOL. We support 2.16.x and 2.15.x currently. And when 2.17 is out, then 2.15.x becomes EOL, and so forth.
On Fri, Dec 18, 2015 at 3:31 PM, ychawla <premiergenerat...@gmail.com> wrote: > Hello All, > I am currently using Camel 2.14.4 for all of our deployments. It uses CXF > version 3.0.5. CXF 3.0.6 has a very nice feature in it which allows support > for legacy SSL connections: > > https://issues.apache.org/jira/browse/CXF-6414 > > With this feature, you can upgrade one server at a time from Java 6 to Java > 8. Otherwise if you upgrade a server, all your web service SSL clients in > java6 will be broken since SSLv2Hello is not allowed in CXF 3.0.5. > > Of course the straight forward solution is to use Camel 2.15.x or even one > of the newer versions. However, there are some conflicts with Spring > dropping OSGi support and this would require a migration to blueprint which > is not possible for our team right now. > > Is it possible to use Camel 2.14.x in karaf with CXF 3.0.6? Does anyone > have any pointers on how to do this? Or will there be a maintenance release > on Camel 2.14.x that will do a minor version upgrade on CXF? > > Thanks, > Yogesh > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-2-14-4-and-CXF-3-0-6-tp5775249.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
