ADF BC: createInsert and partial trigger

Question

I notice when i add a createInsert operation to my page and then the corresponding table, JDev will add a partialTrigger to the button.
I don't see why.
When i press the createInsert, the table should have the partialTrigger, not the createInsert button because the table should be refreshed in order to show the new row. But when i add the partialTrigger to the table, than it like an infinite loop. Table refreshes button, button refreshed table,...
It's resolved by removing the partialTrigger from the button but i am wondering why jdev does it?
I think it has something to do with the disabled state of the button but that does not make sense. THe same for the commit button. If you want everything to work with partialTriggers, then you have lots of buttons/tables linking to each other causing loops or does ADF notices that and takes care of it?

Answer 1

Hi,
I reproduce your case and I do not see any loop,
about your question that why the createInsert need the partialtrigger :
1-first of all it is because of the the disabled attribute which depends on the table
2- Second, the table row selection is automatically partial, I mean when you click on the row partially the selected row is determind as it is done partially there is not any way
for depended components on the table to notify about the state of the tree(changes of row or anything) so the depended component such as CreateInsert need to set the partial trigger.
3-why the table does not need the partialtrigger at the time of drag and drop, the answer is easy because the default button that you drop on the page is not partialSubmit, so why any other depended component like Table, must have the partialtrigger?? it is only needed when the button is partialSubmit,
I hope my answer is clear enough.
to conclude, there is not any mistake or bug from Oracle for sure.