I have a Quartz job that has 3 levels, each level are all asynchronous quartz procedure, and seam components.
Quartz Scheduler -- Calls -- FolderJob -- Calls -- subFolderJob -- Calls -- subSubFolderJob
the first two components just do queries, the last one updates, create or delete about 2000 records per run.
My problem is somehow if an exception is thrown on the last component the rolback is propogated to the first component, and i get no transaction on a query that i dont need to be transactional.
the last component is annotated as @Transactional.
how do i stop the rollback from propagating?
Retrieving data ...