Hi,
Thanks for having handled this.
2016-08-26 22:14 GMT+02:00 Claus Ibsen-2 [via Camel] <
ml-node+s465427n5786774...@n5.nabble.com>:
> Hi
>
> I just fixed the example so we wont forget to do it
> https://github.com/apache/camel/commit/ba6fc872e40b48344330b7bc469892
> e63eb739cc
>
>
> On Fri, Au
Hi
I just fixed the example so we wont forget to do it
https://github.com/apache/camel/commit/ba6fc872e40b48344330b7bc469892e63eb739cc
On Fri, Aug 19, 2016 at 10:08 AM, Claus Ibsen wrote:
> Hi
>
> Thanks for spotting.
>
> You are welcome to log a JIRA and provide a patch / github PR with a fix
>
Hi
Thanks for spotting.
You are welcome to log a JIRA and provide a patch / github PR with a fix
http://camel.apache.org/support.html
http://camel.apache.org/contributing.html
On Fri, Aug 19, 2016 at 9:53 AM, olivier wrote:
> So, i've figured it out by myself. Here is the solution for those who
So, i've figured it out by myself. Here is the solution for those who might
have the same issue.
It seems Camel security 2.17.3 depends on Spring security 4.x...but the
camel-context spring security part of the example is written in Spring
security 3.x, which produces the errors above, because, in