|
From: Rod J. <ro...@in...> - 2004-08-16 12:26:27
|
Eugene, you may want to check your WebLogic license to see whether such decompilation is permitted (I guess it's kind of *your* code, rather = than purely BEA's)... We wouldn't want to advise anyone to violate a = commercial license.=20 -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf = Of j=FCrgen h=F6ller [werk3AT] Sent: 16 August 2004 11:46 To: spr...@li... Subject: Re: [Springframework-developer] Preparing for Spring 1.1 final BTW, Eugene: Have you decompiled your WebLogic EJB proxy to see the resume/forceResume code? In that case, is it obvious to you how WebLogic applies the "transaction-isolation" setting (from its EJB deployment descriptor)? We'd like to provide that for Spring on WebLogic too, but = don't know how to set the isolation level on WebLogic JTA, because the = standard JTA API does not support per-transaction isolation levels... =20 We do already support isolation levels for our native transactions strategies, like DataSourceTransactionManager and co. Our JtaTransactionManager just provides a hook currently; we do not have isolation level support for any JTA backend yet. =20 Juergen =20 |