title: Reliable SOAP Messaging - Use JMS queue or own implementation?
body: <p>I'm confronted with a system (Java, OSGI-based, Equinox, Blueprint) that needs to send asynchronous notifications via SOAP messages to a remote system. The system must ensure that the notifications reach the remote system (i.e. it reponses with a confirmation message, WS-ReliableMessaging is not available).</p>
  
  <p>Now I see two Options:</p>
  
  <ol>
  <li><p>Use the EventAdmin mechanism of OSGI to trigger the notifications, implement my own handler which persists the notification in a queue. A quartz job would poll the queue and try to send the Soap message. The message would only be removed from the queue if the remote system reponses successfully.</p></li>
  <li><p>Use a messaging middleware like ActiveMQ (e.g. as part of Apache Servicemix) to make use of JMS and make the whole task a lot easier.</p></li>
  </ol>
  
  <p>What do you suggest?</p>