;[EMAIL PROTECTED]>
Sent: Friday, July 12, 2002 3:24 AM
Subject: [JBoss-user] Transaction problem
Hi,
The scenario is like this.
1. Jsp will call session bean(Manager) to insert number of records.
2. The session bean(Manager) starts the transaction. And calls the Entity
bean/s in loop.
3. The Sessi
Hi,
The scenario is like this.
1. Jsp will call session bean(Manager) to insert number of
records.
2. The session bean(Manager) starts the transaction. And calls
the Entity bean/s in loop.
3. The Session bean(Manager)commits the
transaction.
I have packaged session bean and all entity b
ay to pass the
instance of the bean that you already have rather than invoke a finder
method.
Cheers,
Richard Doust
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Imran
Bohoran
Sent: Thursday, January 03, 2002 12:23 PM
To: Jboss-User (E-mail)
Subject: [J
What version are you using?
This isn't (exactly) transaction related - the problem is that the
entity isn't stored prior to the finder method. It wouldn't show up if
the entity's methods were marked 'RequiresNew' (not that I'm saying you
want to or should do that!)
This is a bug that (IIRC) w
Hi all
I'm facing a problem which I believe many of you would be having some
solution.
I have a session bean which is deployed with the TRANSACTION attribute as
"Required" and entity beans with the TRANSACTION attribute as "Required" for
all the methods.
I'm setting a value on a entity from my
i am having problems resolving programmatic transactions. What i am running
into is that if you have to create two entity beans in your transaction
block between begin and commit, database connection which i get from
Datasouce for the second bean is not able to understand that i already have
one
