|
From: Mark St G. <stg...@ca...> - 2005-04-22 03:25:37
|
Juergen et al Was looking a bit more into that Hibernate 3.0.1 changelog entry regarding WAS 6 Transaction Manager Factory. Seems to stem from this original Hibernate 3 JIRA issue: http://opensource.atlassian.com/projects/hibernate/browse/HHH-198 I am using Websphere 6 and I did use the same stock config that I had in WAS 5.1. From what I can tell the Transaction Manager Factory class is still: com.ibm.ws.Transaction.TransactionManagerFactory I have started a project (and before downgrading my config back to straight Hibernate transactions) it seemed to work for me. After reading the JIRA issue HHH-198... the user that this stemed from... it looks like he is using WAS 5.1.2? Why are they talking about WAS 6? Anyway, seems a little confusing to me.... I am not sure exactly what they fixed. From Gavin's code in com.hibernate.transaction.WebSphereExtendedTransactionLookup it looks like they implemented an adapter to the Extended JTA Transaction Manager and Transaction... Anyway, I am curious if the Spring transaction management codebase needs an equivilent change? Again, from reading the Hibernate JIRA posts.. and from actually using WAS 6 with Hibernate 3.0 and Spring 1.2 RC2... curious what the issue really is? Thoughts? Cheers, Mark "Juergen Hoeller" <juergen@interfac e21.com> To Sent by: <spr...@li... springframework-d urceforge.net> eveloper-admin@li cc sts.sourceforge.n et Subject Re: [Springframework-developer] WAS 6.0 TransactionManager Lookup 04/21/2005 07:03 AM Please respond to springframework-d eveloper Yes, we should cover WebSphere 6.0 too - I'll do that for 1.2 final. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Dmitriy Kopylenko Sent: Thursday, April 21, 2005 2:01 PM To: spr...@li... Subject: Re: [Springframework-developer] WAS 6.0 TransactionManager Lookup There is WebSphereTransactionManagerFactoryBean which is used to lookup jta TransactionManager implementation for WebSphere versions 4, 5.0, and 5.1, not 6.0 May be we should modify it to add 6.0 lookup code? Dmitriy. Claus Ibsen wrote: >Hi > >I was reading the changelog for Hibernate 3.01 and discovered: >* fixed TransactionManager lookup (again) for WAS 6.0 > >I recall there was something about Spring using a similar strategy to lookup the >TM in WAS as Hibernate does. > >Just though I would raise a flag if there could be a issue. > > >Kind regards > >Claus > > > >------------------------------------------------------- >This SF.Net email is sponsored by: New Crystal Reports XI. >Version 11 adds new functionality designed to reduce time involved in >creating, integrating, and deploying reporting solutions. Free runtime info, >new features, or free trial, at: http://www.businessobjects.com/devxi/728 >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > ------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |