Well, that's just too much work in my opinion. The whole point of using CMT is to simply annotate the class and let the container manage the transaction. Why would I want to use CMT if I have to wrap the EJB inside of another component and manage the transaction myself? A much simpler approach is the simply not use the CMT annotation and allow Spring to manage the transactions from start to finish. In doing so, I don't need to manage the transaction at all. Spring manages it for me and I simply annotate my classes with the Spring @Transacitonal annotation. Problem solved...
If I had know using CMT transactions was going to be so much work I would never have embarked upon the journey. I would have left everything in the hands of Spring to begin with.
[Message sent by forum member 'cmathrusse' (cmathrusse)]
http://forums.java.net/jive/thread.jspa?messageID=290206