Two Levels of Nesting - Composition issue

Support
#1

Hello together,

lower you will find a small Demo Project regarding this issue. Following scenario:

image

Datascource of the Root “Order” Entity Editor is setup correctly:

image

,as described here

But there is one special case, i still get an Error:

  1. I CREATE an new Order

  2. I CREATE an Order-Line inside the Order

  3. I CREATE an Order-Line-Position inside the Order-Line
    image

  4. Before Saving the Order, I delete the Order-Line, i have just created:
    image

  5. I try to save the Order and get the following Error:

image

Here is the Demo Project so you can reproduce the issue:
Test-Project_PERSIST_BUG.zip (100.3 KB)

Thanks for the Help in advance
Daniel

#4

Hi Daniel,

This issue can be solved by setting the allowCommit attribute to false in the 2nd nested datasource:

<datasource id="orderDs"
            class="com.company.testprojectpersistbug.entity.Order"
            view="order-line-posititon">
    <collectionDatasource id="lineDs"
                          property="line">
        <collectionDatasource id="posititonDs"
                              property="posititon"
                              allowCommit="false"/>
    </collectionDatasource>
</datasource>

Thus, the isModified() method of this datasource will always return false, the commit() method of OrderLinePositionEdit screen will do nothing, and all changes will be saved only together with the master entity.

1 Like