Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Summarizing your question: You're looking for a transactionally-safe way to send messages.</p> <h2>Option 1: JMS</h2> <p>Transactionally safe messaging is exactly what JMS is for. There's also good JMS integration in Spring, See the <a href="http://static.springsource.org/spring/docs/3.0.x/reference/jms.html" rel="noreferrer">JMS chapter</a> in the Spring documentation.</p> <p>That will make sure that the messages are sent <em>if and only if</em> the transaction is committed. It also helps for dealing with errors in listeners for these events.</p> <p>A difference with your current setup is that these events will be handled asynchronously: your service will return before these events have been handled. (JMS will make sure that they are processed eventually, it can be configured to try multiple times and how to deal with errors,...). Depending on your needs, that may be a good or a bad thing.</p> <h2>Option 2: Transaction synchronization</h2> <p>Alternatively, if JMS is too <em>heavy-weight</em> for your case, you could use transaction synchronization: When sending an event, instead of sending it directly use Spring's <code>TransactionSynchronizationManager.registerSynchronization</code>, and send the message in the <code>afterCommit()</code> of your <code>TransactionSynchronization</code>. You could either add a new synchronization per event to be sent, or add one synchronization and keep track of which events to be sent by binding an object containing that list to the transaction using <code>TransactionSynchronizationManager.bindResource</code>.</p> <p>I would advise against trying to use your own <code>ThreadLocal</code> for this, because that would go wrong in some cases; for example if inside your transaction you would start a new transaction (<code>RequiresNew</code>).</p> <p>Differences with your current setup:</p> <ul> <li>if an exception is thrown in the handling of the events in this case, your service will throw the exception, but the changes will already have been committed in the database. </li> <li>if one of your listeners also writes into the database, it will have to do so in a new transaction.</li> </ul> <p>Alternatively, you can use <code>beforeCommit</code> instead of <code>afterCommit</code>, but then your events will be handled (mails sent,...) even if the actual commit to the database later fails.</p> <p>This is less robust (<em>less transactional</em>), than using JMS, but lighter and easier to set up, and usually <em>good enough</em>.</p>
    singulars
    1. This table or related slice is empty.
    1. POSending events at the end of a transaction
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USWouter Coekaerts
    1. USWouter Coekaerts
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSending events at the end of a transaction
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1; good point regarding the use of `ThreadLocal` and `RequiresNew`...
      singulars
      1. PO
      1. UShome
    2. COThanks for the reply. We can't use JMS for reasons I won't go into. I'm not sure I understand the problem with using ThreadLocal though (what does `RequiresNew` mean)? If you start a transaction from within a transaction, then that doesn't spawn a new thread does it?
      singulars
      1. PO
      1. USJon
    3. COthanks for the info, I've made it work pretty good with the second option - Transaction synchronization.
      singulars
      1. PO
      1. USdavorp
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload