RE: WebSphere and transaction managers

2007-02-20 Thread Patrick Linskey
Sutter [mailto:[EMAIL PROTECTED] > Sent: Monday, February 19, 2007 6:54 PM > To: open-jpa-dev@incubator.apache.org > Subject: Re: WebSphere and transaction managers > > Craig, > > On 2/19/07, Craig L Russell <[EMAIL PROTECTED]> wrote: > > > > > > On Feb 19

Re: WebSphere and transaction managers

2007-02-19 Thread Kevin Sutter
>> Notice: This email message, together with any attachments, may >> contain >> information of BEA Systems, Inc., its subsidiaries and >> affiliated >> entities, that may be confidential, proprietary, copyrighted >> and/or >> legally privileged, a

Re: WebSphere and transaction managers

2007-02-19 Thread Craig L Russell
, and have received this message in error, please immediately return this by email and then delete it. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Monday, February 19, 2007 8:33 AM > To: open-jpa-dev@incubator.apache.org > Subject: Re

Re: WebSphere and transaction managers

2007-02-19 Thread Kevin Sutter
sage. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Monday, February 19, 2007 8:33 AM > To: open-jpa-

Re: WebSphere and transaction managers

2007-02-19 Thread Craig L Russell
mmediately return this by email and then delete it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, February 19, 2007 8:33 AM To: open-jpa-dev@incubator.apache.org Subject: Re: WebSphere and transaction managers It is possible to suspend a transaction by th

RE: WebSphere and transaction managers

2007-02-19 Thread Patrick Linskey
nt, and have received this message in error, please immediately return this by email and then delete it. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Monday, February 19, 2007 8:33 AM > To: open-jpa-dev@incubator.apache.org > Subject: Re: We

Re: WebSphere and transaction managers

2007-02-19 Thread Kevin Sutter
>> contain >> >> information of BEA Systems, Inc., its subsidiaries and >> >> affiliated >> >> entities, that may be confidential, proprietary, copyrighted >> >> and/or >> >> legally privileged, and is intended solely for

Re: WebSphere and transaction managers

2007-02-19 Thread Craig L Russell
tended >> recipient, >> and have received this message in error, please immediately return >> this >> by email and then delete it. >> >> > -Original Message- >> > From: Albert Lee [mailto:[EMAIL PROTECTED] >> > Sent: Friday, February 16

Re: WebSphere and transaction managers

2007-02-19 Thread Kevin Sutter
l >> or entity named in this message. If you are not the intended >> recipient, >> and have received this message in error, please immediately return >> this >> by email and then delete it. >> >> > -Original Message- >> > From: Albert

Re: WebSphere and transaction managers

2007-02-19 Thread Craig L Russell
recipient, and have received this message in error, please immediately return this by email and then delete it. > -Original Message- > From: Albert Lee [mailto:[EMAIL PROTECTED] > Sent: Friday, February 16, 2007 11:21 AM > To: open-jpa-dev@incubator.apache.org > Subject:

Re: WebSphere and transaction managers

2007-02-19 Thread Kevin Sutter
- > From: Albert Lee [mailto:[EMAIL PROTECTED] > Sent: Friday, February 16, 2007 11:21 AM > To: open-jpa-dev@incubator.apache.org > Subject: Re: WebSphere and transaction managers > > This is known problem in WAS. The reason is data source > created in WAS is > always enliste

RE: WebSphere and transaction managers

2007-02-16 Thread Patrick Linskey
bator.apache.org > Subject: Re: WebSphere and transaction managers > > This is known problem in WAS. The reason is data source > created in WAS is > always enlisted in the current global transaction, therefore > RESOURCE_LOCAL > persistence unit using WAS data source triggers

Re: WebSphere and transaction managers

2007-02-16 Thread Albert Lee
This is known problem in WAS. The reason is data source created in WAS is always enlisted in the current global transaction, therefore RESOURCE_LOCAL persistence unit using WAS data source triggers the observed behavior. This limitation will be corrected in the WAS EJB3 Feature Pack and future re