BIG PROBLEM: Multiple (loop) NOTIFY COMMITS for same VO instance

Question

Dear forum,
I have a big problem with 1 of my VO.
When I insert a record using AddProjectView this works fine. The record is persisted successfully.
When I insert another record using AnotherView (e.g. different table) a commit is also done on AddProjectView.
In de log I can see: AddProjectView notify COMMIT ...
I wouldn't have found any problem if I didn't had a afterCommit on AddProjectView which inserts some records in a table. The inserts fail because UK violations.
Now the problem is, why is AddProjectView being committed again?
If I keep updating records in AnotherView, everytime the AddProjectView is commited. If I stop the running OC4J instance and restart it, the AddProjectView is not committed anymore! It seems the VO instance is keeps 'hanging' around....
As I don't have any idea, any help is appreciated.

Answer 1

Hi,
When exactly you are creating and inserting record in destVO?
mere destVO.first() won't work, first() works if records are already fetched using query.
If I understand correctly, you should be creating new record in destVO (albait the only record) as follows:
Row row = destVO.createRow();
//defaulting logic should go here
row.setAttribute("Attr1", value);
destVO.insertRow(row);
row.setNewRowState(Row.STATUS_INITIALIZED);
Thanks,
Hrishikesh