|
From: Eugene K. <eu...@pl...> - 2004-08-31 00:57:34
|
Colin Sampaleanu wrote: > 'Eu' on his blog 3-4 days ago commented based on my own blog entry, and > a forum message: > http://jroller.com/page/eu/20040826#using_spring_jta_interfaces_from > that section / C.2.4 /of the EJB spec says that the container, for EJBs, > must implement the UserTransaction interface (and JTA 1.0.1) extension, > but doesn't have to implement the other interfaces defined in the JTA > specification. Fine, I've actually seen that before, coincidentally, > when I was tracking something down a while ago, but I think a container > is fundamentally broken if it _does_ expose the JTA TransactionManager > interface, and it doesn't behave as per the spec. The spec for an API is > the spec for the API. If you expose the interface at all, then you need > to expose it correctly... That's essentially how I read that clause, and > how I see things. In any case, I hope the situation is going to improve, > certainly WLS 8 works where WLS 7 doesn't, with out WL specific adapter... Perhaps I wasn't clear enough. My point is that it is a bad idea to mix usage of JTA interface with declarative container managed transacttions for EJBs. In other words it is probably to use Spring JTA helpers/wrappers in web layer which is not using EJB's. Anyway it would be good have some more advanced tests to ensure that JTA actually work in WLS8 (and other containers) in case of failure/rollback with multiple XA resources involved into transaction (especially resources from different vendors, such as Oracle, Sybase, MQSeries). regards, Eugene > Colin > > jürgen höller [werk3AT] wrote: > >> After our recent issues with JTA resume (with the outer transaction >> marked as rollback-only) on WebLogic, which we were just able to solve >> for WebLogic 8.1 but not for 7.0: >> >> http://opensource.atlassian.com/projects/spring/browse/SPR-251 >> <http://opensource.atlassian.com/projects/spring/browse/SPR-251> >> we now have similar problems on WebSphere 4.0, seemingly with >> suspension of an ordinary transaction: >> >> http://opensource.atlassian.com/projects/spring/browse/SPR-295 >> <http://opensource.atlassian.com/projects/spring/browse/SPR-295> >> Any WebSphere user that can shed some light on this? I'm afraid that >> we'll have to invoke some proprietary WebSphere API for JTA >> suspend/resume, just like we had to do for WebLogic... >> >> Oh how do I wish that J2EE considered >> javax.transaction.TransactionManager as proper public API... >> >> Juergen >> >> >> > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |