Hi By all means please report back your findings. This is an interesting use-case that could be useable in the future for others or that we could do / improve something in Camel as well.
Med venlig hilsen Claus Ibsen ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: nitingupta183 [mailto:[EMAIL PROTECTED] Sent: 10. oktober 2008 07:39 To: camel-user@activemq.apache.org Subject: RE: SEDA+Spring Transaction Hi Claus, Yes, from transaction wise no issues. The only issues that can result are because of the thread change. But I think I would have to handle this if I desire asyn behaviour in my app. Will have to do some infrastructure coding in the main app layer for fixing the hibernate session to the consumer thread, but rest all shall work great. Thanks, Nitin Claus Ibsen wrote: > > Hi > > If you get both hibernate and the consumer in the same transaction manager > I think using SEDA or no SEDA should not matter at all. > > SEDA does not handle any transaction etc. > > I don't see any problems here. > > Why don't you try cranking some code together and see how it goes. > > > > Med venlig hilsen > > Claus Ibsen > ...................................... > Silverbullet > Skovsgårdsvænget 21 > 8362 Hørning > Tlf. +45 2962 7576 > Web: www.silverbullet.dk > > -----Original Message----- > From: nitingupta183 [mailto:[EMAIL PROTECTED] > Sent: 30. september 2008 14:36 > To: camel-user@activemq.apache.org > Subject: SEDA+Spring Transaction > > > 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. > > > -- View this message in context: http://www.nabble.com/SEDA%2BSpring-Transaction-tp19741179s22882p19912319.html Sent from the Camel - Users mailing list archive at Nabble.com.
