Business components: detail entity creation

Question

Hi,
Using JDeveloper 10.1.3.1.0.
I've got a master-detail relationship between two entities. To do CRUD operations, I always go through the view objects based on these entities. My problem is when I create a new instance of the detail, it seems the association at the entity level is not maintained before commit.
For example, let's say I have the entities EntityMaster and EntityDetail and the view objects ViewMaster and ViewDetail. There's an association at the entity level and a view link at the view level. This is a one-to-many relationship (one master - many details).
I do the following in an application module method:
ViewObject detailView = getViewDetail(); //returns the detail view object.
Row newRow = detailView.createRow(); //create a new view row backed by an entity row
// initialize the new row
detailView.insertRow(newRow); //insert the row in the view.
// a bit further
EntityMasterImpl master = ...; //obtain somehow a reference on the master.
RowIterator detailEntityIterator = master.getDetailEntity(); //get the detail entity iterator
int count = detailEntityIterator.getRowCount(); //count has not been incremented by one.
Since I have a validation on the master entity that checks if there's at least one detail entity when setting a particular attribute, I really need the association to be maintained at the entity level.
I've worked around the problem by inserting the new detail entity row in the detailEntityIterator like this:
newRow.getDetailEntity().getMasterEntity().getDetailEntity().insertRow(newRow);
It does not seem to me like an elegant solution and I really feel the association should be maintained at the entity level automatically.
Is this a bug or is there any other (more elegant) workaround?
Thank you,
Olivier

Answer 1

Hi Steve,
This is not a composition association. Actually, this is an association from a table to an intersection (many-to-many) table. The code in my service is based on the SRDemo, see SRServiceImpl#updateSkillsForCurrentStaff(List) and is called on a save button from a shuttle page.
The current master is the master I want it to belong to. The link to the master gets correctly saved in the database (just as in the SRDemo). We can also navigate from the master view row to the find the detail view row using the generated RowIterator. However, this does not work from the master entity row to the detail entity row. The problem is really at the entity level.
Thanx
Olivier