When do CMP Entity Beans persist data?

[Lord0]

Hi there,

I've inherited a Struts app running on OC4J/Oracle 10g which uses CMP
Entity beans to handle reading/writing data from the DB.

My question is: WHEN does the container write the data in the beans
back to the DB? (I believe it decides "itself" when to do this)

Cheers

Lord0

 

[Donkey Hottie]

Hi there,

I've inherited a Struts app running on OC4J/Oracle 10g which uses CMP
Entity beans to handle reading/writing data from the DB.

My question is: WHEN does the container write the data in the beans
back to the DB? (I believe it decides "itself" when to do this)

Cheers

Lord0

If there is a session bean managing the entity beans, the transaction
begins when you "enter" a method in that session bean. It ends when you
exit the method.

I think the container have to write the data at least just before the
transaction ends.

 

[Arne Vajhøj]

I've inherited a Struts app running on OC4J/Oracle 10g which uses CMP
Entity beans to handle reading/writing data from the DB.

My question is: WHEN does the container write the data in the beans
back to the DB? (I believe it decides "itself" when to do this)

When the transaction in the EJB container commits succesfully, then
the database update must go through. Even though the EJB specs may
not say how, then I can not see any other way of achieving that
than having the EJB tx commit do a DB tx commit.

The EJB spec also has a little figure that shows a commit to
the database at that point.

With a common EJB config the EJB transaction will commit after the
outermost session bean method call exits before returning to
client.

Also note that if other apps are accessing the data, then you need
to look at the CMP beans deployment descriptor - more specifically
commit option A, B and C.

Arne

 

[Lord0]

thanks for the replies guys

 

[Lord0]

thanks for the replies guys