Message-ID: <195279013.1559.1369230192782.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1558_1372167678.1369230192782" ------=_Part_1558_1372167678.1369230192782 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The transaction implementation is using the Unit Of Work and the UnitOfWorkProtocol aspect to achive completely transparent tran= saction demarcation. You can registers one or many listeners to the Unit Of Work which will be called upon= commit, rollback etc.
Each transaction implementation consists of two parts:
See the UnitOfWorkProtocol= for details on how to define the Unit Of Work aspect, e.g. on which methods a new transaction should = be started, committed and roll backed etc.
The transaction implementations work great in conjunction with the Persistence components, in which it c= an for example make them aware of JTA two-phase commit transactions etc. Yo= u just register your listeners in the Unit Of Work and the complete transaction will not be committed unti= l all listeners have agreed on that.