Wierd functionality of OC4J with BMP EJB....Crazy or is this supposed to happen?

Question

Hi. I'm in a class developing a BMP Entity EJB. I deployed the
bean, whose functionality does simple insert, update, delete
from one table. I created a test client to run from the command
line which works for the create (it inserts a row into the
database). I run SQLPLUS to confirm this.
I then go in to the database through SQL PLUS and delete the row
and commit.
Then I RERUN the test client and the application gives me an
javax.ejb.DuplicateKeyException . Should this happen? When I
look in the database, the ejbCreate is called because the row is
inserted back in, so that much works, but for some reason the
exception is called. Anybody have an idea?
Thanks - Matt

Answer 1

Figured it out thanx to the instructor. Apparently OC4J sets an
EJB setting in the orion-ejb-jar.xml file.
Under <entity-deployment>,
you need to set exclusive-write-access = "false"
The current default is "true"
The default of "true" basically assumes the EJB is the only way
to access the data in the database, so it gives better
performance since data is cached. However, if your application
is used in a distributed environment where you have other
applications working with the data (i.e. Developer App, or
SQLPLUS), then you will want to set this field to "false".