Oh thanks! I was going to raise a jira issue after I verified it worked on
my end.
I removed the extends CamelTestSupport
and removed the
createRouteBuilder in the test class so the route is being created by the
"production" route builder instead.
it worked.
I would be very happy if CamelTest
On 2018/03/21 12:43:25, Claus Ibsen wrote:
> Try to debug the code and step through
Ok, I was hoping to narrow a bit the scope of my search, but if you cannot
provide any
insight, fine.
For reference, this is the full stacktrace:
15:11:42.271 ERROR
org.apache.syncope.core.provisioning.camel
Hi
I logged a ticket to not forget about this, to see if we can improve
it (and detect that the class is IoC'ed by Spring / Spring-Boot and
then avoid the 2x IoC
https://issues.apache.org/jira/browse/CAMEL-12389
On Tue, Mar 20, 2018 at 4:15 PM, Claus Ibsen wrote:
> Hi
>
> Yeah for SB then it ten
Try to debug the code and step through
On Wed, Mar 21, 2018 at 1:34 PM, Francesco Chicchiriccò
wrote:
> On 2018/03/21 12:16:17, Claus Ibsen wrote:
>> Hi
>>
>> I think you should ask the Apache Syncope team as its their
>> integration with Camel.
>> It sounds like some classpath problem.
>
> Well
On 2018/03/21 12:16:17, Claus Ibsen wrote:
> Hi
>
> I think you should ask the Apache Syncope team as its their
> integration with Camel.
> It sounds like some classpath problem.
Well, I am part of the Syncope team :-)
I am asking here because the problem below only occurs after upgrade to Cam
Hi
I think you should ask the Apache Syncope team as its their
integration with Camel.
It sounds like some classpath problem.
On Wed, Mar 21, 2018 at 1:04 PM, Francesco Chicchiriccò
wrote:
> Hi all,
> in Syncope we have a Camel-based extension, whose initialization has been
> working fine so fa
Hi all,
in Syncope we have a Camel-based extension, whose initialization has been
working fine so far (up until Camel 2.20.2) but fails with the recent Camel
2.21.0.
In particular, the following exception is raised during Syncope Core webapp
initialization [1]:
org.apache.camel.RuntimeCamelExc
Hi,
I would try to remove the id/routeId from every route/rest. Then start your
thing and look via jconsole how many instances of your Routebuilder are
actually running.
Cheers, Thomas.
-Ursprüngliche Nachricht-
Von: hrvoje.djurdje...@rba.hr
Gesendet: Dienstag, 20. März 2018 18:59
A
