Details
-
Bug
-
Resolution: Done
-
Major
-
JBossAS-3.2.6 Final
-
None
Description
SourceForge Submitter: waggj .
We are primarily running 3.2.1. Our attempts to go to
higher 3.x versions have run into problems 885357 was
the original problem but this is fixed (in 3.2.4 at least).
However this seems to have led on to another seemingly
related problem.
The scenario is a BMP bean controlling a CMP bean.
ejbCreate is called for the BMP bean. This does a create
for the CMP bean just using key fields in the table.
There are four indexes on the CMP bean's table and all
except for one are composite keys. Only two of the
indexes are unique. Further fields are updated in the
BMP bean after creation. We come to commit the
transaction. ejbStore is called on the BMP bean which
updates the CMP bean. BUT ejbStore is never called on
the CMP bean so the updates are lost. It's as if the
persistence manager has already looked at the CMP
bean, seen that nothing has changed and ruled it out
for update before the BMP bean updates it. The work
around, of course, is to create with all the fields
required rather than just the key fields. But it should
work as it is shouldn't it?
We are running on Windows XP. JDK 1.4.2_03