> > Other examples I find uses routes and policy... but I want > @Transactional. > > Is this possible? I'm really confused. > > It should be. The Camel endpoint will typically set the transaction up > before invoking your bean; so you don't need to create a dynamic proxy > of your bean with a transaction interceptor around it.
Uh? If I use tx:annotation-driven and @Transactional spring does create a dynamic proxy as a transaction interceptor, right? So what are you saying here? > > I wonder if your problem is with the JTA transaction manager; which > depends on an XA aware ConnectionFactory? Maybe using the JMS Probably. I'll take another look at my config in jboss and ems. > > transaction manager might work better; then TibCo doesn't need to do > XA stuff? I really want xa. Speed is not an issue, and I want to be able to read a jms message, update the db, and most importantly send a few jms messages in the same transaction. The first part I guess could be just as good using idempotent consumer, but what about the sending part? If the db commits, one could say that I need to create xml messages for every hibernate mapped entity in the db that has been updated. One xml message per jms message, and all or none should be sent. Maybe it's just my jms knowledge thats lacking? Thanks, /Magnus
