Hi Thomas,
thanks for your reply!
The error message is like I sent it to you.
The message text is possible cutted, this happens not in this mail ;-)
In my sources I do the following:
- read the data (Load) ... commit this transaction
- require new load for the same objects in a new transaction -- failes!
The switch-off for the cache is just our current workaround. We do need
cache, and we do need the possibility to enforce the reload for the object (
at least for different classes from the same base).
Even if I set the whole class hierachie to db-locked, the error occurs.
To reconstruct this behavior I send you my testfiles.
By the way, we implemented a new KeyGenerator. It uses a DB2 feature to
generate unique keys. We can send it if you like.
Katrin.
createTest.sql
Test1.java
Test2.java
Test3.java
TESTDB.xml
testmap.xml
TestTest.java
