This content has been marked as final. Show 2 replies
important: 22.214.171.124 , ADF BC , WLS 10.3.5. is not correct - it should be WLS 10.3.6
For the tree building, its not the view links you defined on the ADF BC data model but the view links physically defined for the View Objects. Only the top level node view object is really read from the data model, the rest then is looked up by implicit accessors created. So while there is a way to have two child node collections, its not from view object instances you define and configure using view criteria
though this sample is on JDeveloper 10.1.3, it still works in 11g. What it shows is how to filter child rows in a tree based on some criteria
Thanks for your reply Frank.
important: 126.96.36.199 , ADF BC , WLS 10.3.5. is not correct - it should be WLS 10.3.6AFAIK , 188.8.131.52 is compatible with both WLS 10.3.5 and 10.3.6 WLS and comes out of the box with WLS 10.3..5 which I am using for the Integrated Server.
So while there is a way to have two child node collections, its not from view object instances you define and configure using view criteriaThe link you posted above is simialr to another link I bumped into yesterday -
"How to filter tree node child data" , Pg 12 @ http://www.oracle.com/technetwork/developer-tools/adf/learnmore/feb2011-otn-harvest-328207.pdf written by you.
But my requirement is showing instances of the same EmployeeVO as two tables inside the Department Iterator. But I am not able to do that since there is only one ViewLink accessor for the EmployeeView.
Is that even possible without using 2 explicit physical View Links ?