Hello, We have a large file that we would like to transactionally read row by row into a database using Bindy objects without blowing up the Java heap.
Several attempts has been made using nested Split EIP and SQL producer with batch constructs. One of them we used a combination Split & Loop EIP with temp files. In that process we discovered that the Loop EIP doesn't copy the "Transacted" state from the exchange in the route and then SQL producer will update the database with AutoCommit. First question is that intended and if so is it documented or should that be reported as a bug? The second question is if anyone else has solved this problem and are willing to give us som tips? Mvh / Best regards, Håkan Lantz
