|
From: <jas...@ma...> - 2004-10-28 08:24:16
|
On 27 Oct 2004, at 20:11, Eugene Kuleshov wrote: > James Strachan wrote: >>> I think Eugene has a point. >>> >>> The work manager isn't the problem, it's integrating message >>> delivery to mdbs without container support. This is going to be >>> even more unlikely to work for CMT mdbs. >>> >>> If you want to use your spring psuedo-mdbs inside a j2ee container, >>> there's still the problem of transactional message delivery. >>> There's no standard way to find the TM and even if you get it I >>> would investigate extensively before thinking that using it directly >>> will give you the correct semantics. >> Agreed - though we're delegating to Spring for this issue.... > > By the way, there was a huge discussion related to CMT and Spring > manged transaction and as far as I remember everybody agreed that in > general it is a bad idea to mix those. BTW I think its worth saying, that in all the projects I've used JMS (which is most of them over the last 5 years), I think I use XA delivery less than 2% of the time. So for 98% of the time at least, I tend to use regular JMS with no transactions and just use the regular JMS acknowledge() or commit() mechanisms, which requires no J2EE transaction manager or special container hooks whatsoever. So even if the JCA Container never supported J2EE transactions or didn't support them any where near as well as a full J2EE container, its still very, very useful IMHO. James ------- http://radio.weblogs.com/0112098/ |