PassivateStateForUndo stores temporary DBSequence after db error ?

Question

I'm noticing something strange with our DBSequence attributes, perhaps you could help us out here.
Whenever we try to create a new Entity instance a temporary negative value is generated for the DBSequence attributes (which is correct). Then, when we Commit the outstanding changes. Before posting our changes to the database, we use "passivateStateForUndo" to create a savepoint for the ApplicationModule.
Next, a "before insert row" trigger is waiting in the database to create a new value using a sequence. But, we have a number of business rules implemented using PL/SQL and when one of them raises a ORA-exception we call "activateStateForUndo" to revert to the previous state.
When we modify our data, so our business rules are all validated ok, and commit the changes ... the Entity is succesfully stored in the database using the "temporary negative number". When we query the db we see, for example, ID = -16. This tells us that the temporary value is actually passed to the database.
This is the code in the trigger we use to generate a new value :
      IF (br$row.ID IS NULL)
      THEN
         SELECT rbs_klm_seq.NEXTVAL
           INTO br$row.ID
           FROM DUAL;
      END IF;The described behaviour is not displayed when, for example, a mandatory attribute is left empty. This is caught on the middle tier before any changes get posted to the database.
Could it be that the passivateStateForUndo is passivating just a little too much ? Should the temporary negative value for DBSequence attributes really be posted to the database in the postChanges(TransactionEvent) ?
In other words, am I missing something ? Or is this overeagerly behaviour of the passiveStateForUndo / activateStateForUndo method ?
We're using :
==========
- Jdeveloper 10g 10.1.2.1.0 (build 1913)
- Jheadstart 10g 10.1.2.1 (build 27) --> But, my guess is that Jhs has nothing to do with this issue.
Regards,
Pascal Prins

Answer 1

As you can see in your plsql statement you test for null values only.
In my opinion you should add a test if sequence is negatif to your condition.
We use sequences:
1) Sequence fetched in ADF create method
2) Sequence fetched in DB pre-insert trigger
When 2) is implemented we check the flag requery on insert in the entity and the condition is:
field is null or field < 0 => select sequence
Hope this helps.
Regards
Fred