Hello guys,
i need your support on a project i am currently working on. I have the following data model, i am representing it based on the datasource of the “root” entity Controller :
So basically we are talking about a three level one-to-many relation (Composition). the issue/behavior i am facing is:
- when adding an “interessentZeitraum” object (the third level) via the given controllers, it is stored correctly in the database
- when changing a property of or deleting an “interessenZeitraum” object, this action will not be stored in the database.
- when changing a propetery / deleting an object and at the same time adding at least one new object, all changes will be stored in the database
So in every “preCommit” statement of the three controllers containing “interessentZeitraumDs” as a nested collection datasource, i added a syso-print of the Datasource Context, and noticed the following:
-
When adding an object to interessentZeitraumDs:
-
When changeing or deleting an object of/from interessentZeitraumDs:
So it loses the modified state in the “root” controller “auftragsanfrage”. but as i said, it works fine when adding a new “interessentZeitraumDs” object.
Also, when i print “interessentZeitraumDs.size()” in the “root” controller:
- when adding an object as mentioned above: it gives me the correct number of objects in the collection
- when deleting / changeing an object as mentioned above: it always results in zero.
so only when actually adding at least one “interessentZeitraum” object, does the “root” controller, responsible for propagating the changes to the db, contain the objects of the datasource, otherwise the datasource is always empty.
Can someone maybe point me in the right direction? Do i need to check my Datasource setup in the controllers? all other nested collections within that “auftragsanfrage” entity / controller work as they should.
Thanks in advance
Daniel