f danch
> Sent: Friday, November 02, 2001 3:12 PM
> To: David Jencks
> Cc: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] DB connection/transactions in the same J2EE
> transaction context.
>
>
>
>
> David Jencks wrote:
>
> > If you are depending on the changes b
connection/transactions in the same J2EE
transaction context.
David Jencks wrote:
> If you are depending on the changes being sent to the db in a certain
> order.. this may not be happening, I'm not sure. I think right before the
> end of the transaction all ejbStore methods g
To add a little more information to this scenario. The connection pool is
using the oracle jdbc 1.1.1 driver using the
org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl wrapper for the DataSource.
(We have issues with the jdbc 1.2 driver not related to this)
We tested this scenario with just two b
David Jencks wrote:
> If you are depending on the changes being sent to the db in a certain
> order.. this may not be happening, I'm not sure. I think right before the
> end of the transaction all ejbStore methods get called, but perhaps not in
> any particular order.
>
I believe that 2.4.3
If you are depending on the changes being sent to the db in a certain
order.. this may not be happening, I'm not sure. I think right before the
end of the transaction all ejbStore methods get called, but perhaps not in
any particular order.
If you are using non xa connections ("local transaction
I am hoping to find a simple resolution to this problem. I am running JBoss
2.4.3
I have a SLSB that is used for persisting business objects implemented as
simple java beans. These beans have "alter egos" as Entity Beans in the app
server. (in fact, corresponding entity beans are simply facades f
