For me I am able to get around this by removing myTemplate from
jsonRPCProcesor and fileUploadProcessor. Now my jsonRPCProcessor look
something like below:-
and annotated the ProducerTemplate in my code with @EndPointInject
@EndpointInject
protected ProducerTemplate myTemplate;
Hmm, this just works for me. Note "productHelper" also has the cyclic
dependency.
On Wed, Jul 6, 2016 at 5:56 PM, Debraj Manna
wrote:
> No it is not working.
>
> I think the issue is not because of the separate xml files. It is because
> jsonRPCProcessor is using myTemplate and myTemplate is def
No it is not working.
I think the issue is not because of the separate xml files. It is because
jsonRPCProcessor is using myTemplate and myTemplate is defined in
camelContext and camelContext is using jsonRPCProcessor in routes.
On Wed, Jul 6, 2016 at 2:16 PM, Tadayoshi Sato
wrote:
> No, in the
No, in the same camelContext.xml file but outside of .
Doesn't that work for you?
On Wed, Jul 6, 2016 at 5:34 PM, Debraj Manna
wrote:
> Are you saying to define jsonRPCProcessor inside camelContext. Something
> like below:-
>
> http://camel.apache.org/schema/blueprint";
> useMDCLogging=
Are you saying to define jsonRPCProcessor inside camelContext. Something
like below:-
http://camel.apache.org/schema/blueprint";
useMDCLogging="true">
**
*...*
**
http://0.0.0.0:/orchestratorservice"; />
Hi Debraj,
Then why can you not define jsonRPCProcessor in camelContext.xml instead of
blueprint.xml? If this processor depends on a specific producer template
("myTemplate") == Camel context, then I see no reasons this producer can be
shared across multiple Camel contexts.
On Tue, Jul 5, 2016 a
Yeah Tadayoshi. jsonRPCProcessor is using myTemplate as shown below:-
whereas myTemplate is defined in camelContext which in turn is using
jsonRPCProcessor as shown below:-
http://camel.apache.
Hi,
It looks like 'myTemplate' is defined in camelContext.xml, but the Camel
context then refers to 'jsonRPCProcessor' in blueprint.xml, which in turns
refers to 'myTemplate'. That should be the cyclic dependency in question.
Hope this helps,
Tadayoshi
On Mon, Jul 4, 2016 at 10:27 PM, Debraj Ma
It seems the error is getting triggered because of some cyclic dependency.
But I am not able to figure out from the trace what is causing the cyclic
dependency.
On Jul 4, 2016 4:22 PM, "Debraj Manna" wrote:
> On placing a bundle (using camel) on Karaf I am seeing the below
> exception. The below
On placing a bundle (using camel) on Karaf I am seeing the below exception.
The below exception comes only when the bundle is started. After that
everything works fine. The exeception does not seem to effect our
functionality. The issue is coming on both camel 2.16.1 (deployed on servicemix
6.1.0)
10 matches
Mail list logo