Hello,

I have an application that is using CXF (Soap over JMS) under Websphere 6.1
using EJB3 (and Spring for the CXF configuration part). We are currently
publishing "events" (fire&forget WS call) to an ESB when some logic in the
application is executed (e.g. a new customer has been created etc.).

The problem is that the event is published, even though the commit gets
rolled back because an exception occurs after the event has been published.
Another problem is that when the event is published, the data has not been
committed to the database yet, resulting in the application sending the
wrong data once a subscriber for the event wants to get the data from the
application.

Is there any way to make CXF wait with putting the event message on the JMS
queue until everything is committed? We are using container manager
transactions, and I preferably would like to keep it that way...

Thanks in advance and kind regards,

Robert.

Reply via email to