It's not a workaround, it's by design. And by the way, if you use a splitter instead, you cannot use a single transaction because the splitter will use it's own thread(s).
Best, Christian On Thu, May 17, 2012 at 12:46 AM, dmhatre <darpan27...@gmail.com> wrote: > Hi Folks, > I figured out some workaround for this problem. I dont know whether this > is the proper way to do it or is it something that can be enhanced in > camel. > I went throught the JpaProducer and found out that the > expression.evaluate looks for some kind of convertor else picks default > convertor and exactly where my code was failing since it was trying to > match > arraylist to the entity. > > Below is the workaround that I implemented and was able to successfully > do the batch insert. > <route> > <from uri="file:D://cameldata/test"/> > <process ref="jpaProcessor"/> > <to > > uri="jpa:org.apache.camel.example.spring.DarpanTest?entityType=java.util.ArrayList"/> > </route> > > Look forward to hear some more inputs if possible on this issue. > Thank You! > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Help-with-bulk-insert-using-Spring-JPA-hibernate-tp5710457p5711171.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
