The UnitOfWorkProtocol aspect makes the Unit Of Work management transparent in the user code.
It will allow you to write your code like this:
Instead of like this:
and still all the transaction and persistence management will take place.
The UnitOfWorkProtocol aspect has four abstract pointcuts that you have to define in your XML definition file (a "transactional object" is an object that is set to participate in the Unit Of Work transaction, meaning that the Unit Of Work will keep track of its state):
txRequries- picks out all points in the code where you want a TX REQUIRES transaction to begin, commit and rollback
txMandatory- picks out all points in the code where you want a TX MANDATORY transaction check to occur
txNever- picks out all points in the code where you want a TX NEVER transaction check to occur
transactionalObjects- picks out all transactional object, this pointcut is used by the Transactional Mixin
transactionalObjectCreationPoints- picks out all points in the code where a transactional object is created
transactionalObjectModificationPoints- picks out all points in the code where a transactional object is being modified (best done with a
Here is an example on how to define this in XML: