Menu
▾
▴
springframework-developer
|
From: Claus I. <cib...@ya...> - 2005-04-21 08:44:49
|
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 |
|
From: Dmitriy K. <dko...@ru...> - 2005-04-21 12:01:40
|
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 > > |
|
From: Juergen H. <ju...@in...> - 2005-04-21 12:04:45
|
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 |
|
From: Mark St G. <stg...@ca...> - 2005-04-21 15:51:53
|
Hi Juergen,
I am using WAS 6, Spring 1.2 RC2 and Hibernate 3.0 ... I am pretty sure the
standard Transaction Manager Factory lookup still works.
i.e. WebSphereTransactionManagerFactoryBean
private static final String FACTORY_CLASS_5_1 =
"com.ibm.ws.Transaction.TransactionManagerFactory";
I think the stuff Gavin has in the
org.hibernate.transaction.WebSphereExtendedJTATransactionLookup is
to support the WebSphere JTA extensions to the spec..... basically
transaction synchronization callbacks.
That said, I still think the Spring WebSphereTransactionManagerFactoryBean
needs to change... or
a more likely create a new
WebSphere(6/Extended)TransactionManagerFactoryBean.
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
|
|
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 |
|
From: Juergen H. <ju...@in...> - 2005-04-24 14:12:03
|
Hi Mark, It would be great if you could double-check that our current WebSphereTransactionManagerFactoryBean works properly on WebSphere 6.0! The main feature to test here is transaction suspension as provided by Spring's JtaTransactionManager, through specifying PROPAGATION_REQUIRES_NEW for methods that will be run within an existing transaction. This should lead to suspend and resume calls on the JTA TransactionManager, as located by WebSphereTransactionManagerFactoryBean. If transaction suspension works properly on WebSphere 6.0, I see no need to change anything, in particular no need to use WebSphere's extended JTA synchronization mechanism. I couldn't figure out what actual problem they encountered in Hibernate either... but it seemed to have to do with JTA transaction synchronization, which they need - but we don't. The advantage of Spring's JTA usage style is that the JTA UserTransaction is perfectly sufficient as long as you don't need transaction suspension. Only when using PROPAGATION_REQUIRES_NEW or PROPAGATION_NOT_SUPPORTED and actually encountering an existing transaction, a JTA TransactionManager reference has to be provided. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Mark St Godard Sent: Friday, April 22, 2005 5:19 AM To: spr...@li... Subject: Re: [Springframework-developer] WAS 6.0 TransactionManager Lookup 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 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Mark St G. <stg...@ca...> - 2005-04-24 21:11:49
|
Hi Juergen,
I did a little double-checking with WAS 6 and the
WebSphereTransactionManagerFactoryBean.
I created 2 services (Service A and Service B), each of which delegate to a
DAO (Hibernate implementations) to persist one record .
Service A
-> Service B -> DAO B
-> DAO A
PROPAGATION_REQUIRES_NEW
I configured Service A to use standard REQUIRED and Service B to use
REQUIRES_NEW
I tested having Service A call Service B, and I verified that Service B
definitely runs in its own txn.
The outer transaction (Service A) suspends and resumes, even when the inner
(Service B) txn rolls back.
PROPAGATION_NOT_SUPPORTED
I also tried Service B with NOT_SUPPORTED regarding transaction suspension
/ resume
and I expected that the outer transaction to commit and the inner
transaction to have "no transactionality".
However, from looking in the database, I see 2 records.
It seems that the Service B transaction is committed when I expected there
would be no transaction.
The outer transaction should have no affect on the inner (NOT_SUPPORTED)
transaction. (correct ?)
Anyway, I will investigate further... however after testing this a few
times.. it seems that NOT_SUPPORTED propagation
isnt working on WAS 6...
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/24/2005 09:11
AM
Please respond to
springframework-d
eveloper
Hi Mark,
It would be great if you could double-check that our current
WebSphereTransactionManagerFactoryBean works properly on WebSphere 6.0!
The main feature to test here is transaction suspension as provided by
Spring's JtaTransactionManager, through specifying PROPAGATION_REQUIRES_NEW
for methods that will be run within an existing transaction. This should
lead to suspend and resume calls on the JTA TransactionManager, as located
by WebSphereTransactionManagerFactoryBean.
If transaction suspension works properly on WebSphere 6.0, I see no need to
change anything, in particular no need to use WebSphere's extended JTA
synchronization mechanism. I couldn't figure out what actual problem they
encountered in Hibernate either... but it seemed to have to do with JTA
transaction synchronization, which they need - but we don't.
The advantage of Spring's JTA usage style is that the JTA UserTransaction
is
perfectly sufficient as long as you don't need transaction suspension. Only
when using PROPAGATION_REQUIRES_NEW or PROPAGATION_NOT_SUPPORTED and
actually encountering an existing transaction, a JTA TransactionManager
reference has to be provided.
Juergen
-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Mark St Godard
Sent: Friday, April 22, 2005 5:19 AM
To: spr...@li...
Subject: Re: [Springframework-developer] WAS 6.0 TransactionManager
Lookup
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
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
