Hi Peter,
I'm not claiming guru-hood, but as far as I know you CAN'T do that cleanly.
My thoughts on your best options are:
1) Tell Orion that the entity beans do not have exclusive write-access to
the database by setting exclusive-write-access="false" in the
orion-ejb-jar.xml (which is
t this data), which as you see is a major overhead
Any thoughs on how i best model this.
cheers
-Original Message-
From: Nick Newman [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 12, 2000 5:08 PM
To: Orion-Interest
Subject: Re: Invalidating an Entity bean
Hi Peter,
I'm not claim
er 12, 2000 5:08 PM
To: Orion-Interest
Subject: Re: Invalidating an Entity bean
Hi Peter,
I'm not claiming guru-hood, but as far as I know you CAN'T do that cleanly.
My thoughts on your best options are:
1) Tell Orion that the entity beans do not have exclusive write-access to
the database by setti
Have you tried putting a "required" in the transaction for the entity bean?
Also, if the session bean is not using the entity bean to make the change in
the table, you can't use any of the j2ee transaction stuff. I would only
change the table 2 through the entity bean. You can do that in the
