Re: Error occurred during starting Camel because of cannot look up a processor from registry

2016-07-04 Thread Tadayoshi Sato
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

Re: Schematron files accessed over http

2016-07-04 Thread ayache.k
Hi James Unfortunately, the current implementation of Camel Schemaron only supports classpath and filesystem location for the rules. Create A Jira ticket and I am sure someone would look at. Thanks -- View this message in context:

Re: Error occurred during starting Camel because of cannot look up a processor from registry

2016-07-04 Thread Debraj Manna
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

Re: Help with Topology

2016-07-04 Thread Claus Ibsen
Hi I think you wrote to the wrong mailing list. This is about Apache Camel, not Apache Storm. On Sun, Jul 3, 2016 at 9:15 PM, Sherwin Pinto wrote: > Hi, > > I am using a Trident topology to process files, transform them from CSV, EDI, > XML to a general JSON format. I have

Error occurred during starting Camel because of cannot look up a processor from registry

2016-07-04 Thread Debraj Manna
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)

Why does JPA batch update rollback transaction on single record failure?

2016-07-04 Thread raffi
We're using the following to aggregate messages containing objects bound for JPA/Hibernate endpoint. The problem we have is managing failures; if a single record fails, the entire batch rolls back, and it's difficult to identify which record actually failed. Would be nice if BatchUpdateException