Hi all,

I am very new to SEDA & Transaction concepts. Please tell me what will
happen to the transaction scope between producer and consumer when using
SEDA component.
I am using HibernateTransactionManager with transaction boundaries at the
service layer. From one of the service methods, I want to call the producer
to be able to send a message to a consumer. Consumer is also a  service
layer which has to be in a transaction to perform some underlying DB
operations.

My only requirement is that the consumer should be aware of the transaction
result of the producer service. Consumer should either rollback or should
not fire the db updates if there is any exception in the producer. This is
not required otherwise i.e. producer will finish transaction regardless of
the consumer.

Any help in how I can acheive this while still using SEDA will be lot
appreciated.

Regards,
Nitin
-- 
View this message in context: 
http://www.nabble.com/SEDA%2BSpring-Transaction-tp19741179s22882p19741179.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to