title: JPA @Transaction
body: <p>It seems to me that the common way of starting / stopping a transaction with Spring JPA is to annotate a public function with @Transactional</p>
  
  <p>What I am not able to figure out is if it is possible to annotate a class to make the scope a bit wider.</p>
  
  <p>Lets say that you have a webservice that invokes 3 functions, for the two first you wish to manipulate the data and leave it in the memory attached to the session, but on the third call you wish to store the changed entities. What is the best practice for this?</p>