New detail rows not showing

Question

Hi,
Here's a little background on my problem. We have a simple master-detail hierarchy. Both have a ViewObject. The problem lies in the fact that our detail VO has a filter using a bind variable. The bind variable value is determined (most of the time) at the VO execution time: bindParametersForCollection is overriden and passes a value for the bind variable if it is null. In our specific case the variable represents the username of the authenticated user.
The main complexity lies in the UI. We present all the masters and their children in a single table in edit mode. We are using a tree binding with an accessor from the master node to the child node.
Example
Row 1: Master 1 Column 1 | Master 1 Column 2 | Master 1 Detail 1 Column 1 | Master 1 Detail 1 Column 2
                                             | Master 1 Detail 2 Column 1 | Master 1 Detail 2 Column 2
                                             | Master 1 Detail 3 Column 1 | Master 1 Detail 3 Column 2
Row 2: Master 2 Column 1 | Master 2 Column 2 | Master 2 Detail 1 Column 1 | Master 2 Detail 1 Column 2
                                             | Master 2 Detail 2 Column 1 | Master 2 Detail 2 Column 2
                                             | Master 2 Detail 3 Column 1 | Master 2 Detail 3 Column 2
Row 3: Master 3 Column 1 | Master 3 Column 2 | Master 3 Detail 1 Column 1 | Master 3 Detail 1 Column 2
                                             | Master 3 Detail 2 Column 1 | Master 3 Detail 2 Column 2
                                             | Master 3 Detail 3 Column 1 | Master 3 Detail 3 Column 2Everything works until we try to create new rows. In our use case, whenever we create a new master row, we also create a fixed number of detail rows. The number of detail rows depends on the context. Whenever we do this, the details rows do not show up in the UI.
In my experimentations, I found that the problem was caused by the bind variable on the detail VO. Tracing the detail VO query execution I came to the conclusion that unposted rows where rejected from the QueryCollection when there’s a bind variable. The debugger shows that in VO#executeQueryForCollection the QueryCollection#mUnpostedRows list is empty when there’s a bind variable while it is not when there’re no bind variable.
This is a major issue in our case, so I would like to know if you consider this as a bug (in my opinion it is). If yes, when can we expect a fix or workaround? Otherwise we’ll have to get around this problem by either finding a way to remove the bind variable OR do everything manually in a managed bean (which I would prefer not to have to do).
I have reproduced the problem in a SRDemo test case. Test case has been sent to Steve Muench.
Thanx!
Olivier

Answer 1

This looks very similar to Bug# 6412612 "New Row Lost After Executequery In Vo W/ Bind Variable In Where Clause", reported in the Tech Preview #2 release, and fixed in Tech Preview #3 (due out before the end of December 2007). Will try confirming with an in-house TP3 build that this fix fixes your testcase, too.