Finders/CMP transactions

Question

Hello,
I've got some weird behaviour happening on my finders.
I've got a CMP bean and a Session bean on top of it.
The session bean has a method that performs the following:
1 - creates an instance of the CMP bean
2 - updates an attribute on this instance of the CMP
3 - perform another find on the CMP.
Now the first 2 steps are ok. The 3rd step is a problem.
If I do a find by PK then it works.
But if I perform a custom finder that specifies one of the attributes that was updated in step 2, (eg, age=1, where age is an attribute on the CMP etc), then it doesn't return the CMP.
If I retrieve the bean at this point in time through a find by PK and check the updated attribute, it returns the updated value.
So it is as if the custom finder is some how executed in a different transaction from the rest of the method, as it doesn't see the fact that I've updated the attribute in step 2.
Note that if I call the custom finder in step 1, after creation, it works properly.
I've got the transaction attribute on the session bean to Requires and all the entity bean methods are set to Requires.
BTW, I'm using OC4J 1.0.2.2.1.
Any ideas,
Thanks!!!,
Ricky

Answer 1

you can find DuplicateKeyException is this place
http://java.sun.com/j2ee/1.4/docs/api/
javax.ejb.DuplicateKeyException.
DuplicateKeyException - exception javax.ejb.DuplicateKeyException.
The DuplicateKeyException exception is thrown if an entity EJB object cannot be created because an object with the same key already exists.
But I cannot find how to use DuplicateKeyException in SAP applications
Very Sorry.