use RequiresNew in the entity transactions...
this will (hopefully) ensure JIT use of the critical entities, but at the
cost of data integrity (there she goes again....)
HTH
JP
-----Original Message-----
From: Thomas [mailto:[EMAIL PROTECTED]]
Sent: Viernes, 08 de Diciembre de 2000 11:24
To: Orion-Interest
Subject: if it is possible to have 2 entity beans with same PK existing
in orion ??
dear all,
as title, if it is possible to have 2 entity beans with same PK existing in
orion bean pool??
and if possible, how can i ''force" orion to do so ?
my current problem is:
as my business logic in an entity bean is quite time-consuming
so, when client1 holding that bean to do something
client2 may need to wait for a long time until client1 releasing the bean
(sometimes may even through a deadlock exception),
so if it is possible to clone() another bean with same PK to service
client2 ??
or, if i need to implement transaction tag in its DD to make this possible
??
many thanks !!!
thomas
