]
Marek Novotny updated JBSEAM-4512:
----------------------------------
Fix Version/s: 2.3.0.Final
(was: 2.3.0.ALPHA)
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL:
https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam 2
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Fix For: 2.3.0.Final
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
For more information on JIRA, see: