We have many service methods that are performing read only queries, however they are creating writeable transactions with propagation support to do this. This is causing a number of spurious problems, often manifesting itself by automatically triggering saving of objects which is not intended.

*This may also trigger updates at earlier than expected times, thus causing failures by premature saves. This is due to the default flush policy in use.

We need to review every service method to verify correct transaction usage and behaviour. Only methods which are altering the state of the system should be establishing transactions.