simulate a multi-page transaction or not ?

[codelion]

In Yuan & Heute's book version 12/6/2006 in section 9.4 "Simulate a Multi-page Transaction" ...

method confirm() is annotated @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) and contains a call em.flush().

Per javax.persistence.EntityManager though for method flush() it @throws TransactionRequiredException if there is no transaction.

You see that, TransactionAttributeType.NOT_SUPPORTED would trigger that @throws TransactionRequiredException if there is no transaction, right?

Is section 9.4 speculation (as of 12/6/2006) or is anyone really using it? Any insights?

[codelion]

Seems the right way to do this instead is in seam_reference.pdf (I'm using CVS 20070111) section 6.8. Seam-managed persistence contexts and atomic conversations.

Don't forget to read section 13.4. Seam managed transactions.

Does this mean Yuan & Heute's section 9.4 "Simulate a Multi-page Transaction" will become or is outdated? Since Seam 1.1?