ADF BC - Controlling Entity Posting Order when deleting

Question

Hello,
I'm trying to remove detail and master entity. Default posting order is wrong so I'm getting:
ORA-02292: integrity constraint (DET_MAST_FK) violated - child record found.
All examples are for insert, not delete.
This code in master entity postChanges method doesn't work:
    public void postChanges(TransactionEvent e) {
        if (getPostState() == STATUS_DELETED) {
            RowIterator ri = getDetails();
            DetailImpl detail = (DetailImpl)ri.first();
            while (detail != null) {
                if (detail.getPostState() == STATUS_DELETED) {
                    detail.postChanges(e);
                detail = (DetailImpl)ri.next();
        super.postChanges(e);
    }because getDetails() returns empty RowIterator. It is empty probably because this entity (master) is already deleted.
Has somebody solution how to delete these entities without composition and cascade delete enabled?
Rado

Answer 1

This is exactly what I do.
In MasterImpl.java:
    public void cascadeDelete() {
        RowIterator ri = getDetails();
        //deletedDetails = new ArrayList<DetailImpl>();
        while (ri.hasNext()) {
            DetailImpl detail = (DetailImpl)ri.next();
            //deletedDetails.add(detail);
            detail.remove();
        remove();
    }This method works ok. All entities are removed.
The problem is that entities are not posted in this order. Master postChanges() will not be invoked as the last. It must be the last. I must control it and what I'm looking for is how to do it.
Master postChanges should look like:
    public void postChanges(TransactionEvent e) {
        if (getPostState() == STATUS_DELETED) {
            [... invoke postChanges of all details with STATUS_DELETED ...]
            //if (deletedDetails != null) {
            //    for (DetailImpl detail : deletedDetails) {
            //        detail.postChanges(e);
        super.postChanges(e);
    }The part [... invoke postChanges of all details with STATUS_DELETED ...] is problematic because accessor getDetails() is empty RowIterator (deleted entities are not visible in it). This is why I wrote code which is remarked in this example.
Methods cascadeDelete and postChanges are invoked in two separated html requests.
Rado