|
From: Les A. H. <le...@ha...> - 2004-06-28 21:17:29
|
Quoting sk...@fe...: > By transactions and JMS I assume you mean a transacted JMS Session with > some support for that in the P2pTemplate or the PubSubTemplate for commits > and rollbacks. I don't see that level of support in there currently. I just may have to play with the source code then ;) > But really it sounds to me like you need to manage event propagation with > some type of bean transaction. Iff, if and only if, your transacted bean > does something good put a message on a JMS Destination. It doesn't sound to > me like your having JMS problems but general transaction flow problems. > That is your, messages were being sent fine, until you started tweaking the > nobs, but are being sent at the wrong time in a transactions lifecycle. Yes, thats exactly what is happening. However, in a Spring environment, I was hoping that I could configure my JMS publisher to "send-on-commit" only, instead of sending immediately during the middle of a transaction. This is occurring in a POJO that is proxied by a TransactionProxyFactoryBean, so the transaction management is done via Spring (by using the J2EE UserTransaction). I guess to achieve that behavior in Spring managed transaction would be to have the JMS session managed by Spring as well? I wonder if using a TransactionTemplate would help in the interim. I'll keep chugging... Regards, Les |