title: Hibernate transaction boundaries
body: <p>I'm using Hibernate (in a Grails app) and the transactional boundaries are service methods, i.e. every time a service method is called a transaction starts, and every time a service call completes the transaction is either rolled back or committed.</p>
  
  <p>If one of the database operations causes a database trigger to fire, and this trigger makes changes to persistent data, will these changes be rolled back or committed when the service call completes, or are changes made by the trigger "outside" the transaction?</p>
  
  <p>Thanks,
  Don</p>