I have two discrete saves that needed to be wrapped as a single transaction. It is not clear how to do this. I have tried the following:

@Transactional(propagation=Propagation.REQUIRES_NEW, rollbackFor=Exception.class)
controller() method
--- prepares first data set by creating domain objs and populating values
--- invokes method A that uses em to persist
--- prepares second data set by creating domain objs and populating values
--- invokes method B that uses em to persist

both method A and method B, residing in other service objs, have @Transactional annotation also.

How can I ensure that the controller method rolls back if either method a or b fail? Do I both persist and flush on both A and B or just persist at that level and then Flush at the controller level?

You mean something like this?:

Thanks for the reply. That is indeed what I mean. I am however, using Container-managed transactions. I am having a difficult time getting this type of transaction set to work. I am using Spring, AOP and Hibernate and I can not get my @Transaction and EntityManager to work as I want. I can get A and B to work but I can not get the main part to control the logical unit. So in the CMT world want the following:

@Transaction
class1.transManager()
{
// start transaction here
EntityManager em = getEntityManager()
try
{
class2.doA()
class3.doB()
em.flush()
}
catch
{
em.clear
}
}

class2.doA (Join the transaction started above)
{
EntityManager em = getEntityManager()
try
{

em.persist(stuff)
}
catch
{
throw
}
}

class3.doB (Join the transaction started above)
{
EntityManager em = getEntityManager()
try
{

em.persist(stuff)
}
catch
{
throw
}
}

Maybe I should not use CMT but maybe manage it at a session level. Any thoughts?