Building tree using view crateria in view objects

Question

suppose that i have the following tables "class" ,"group" and "item".
items in table "item" belong to groups in table "group" and groups belong to classes in table "class" .
suppose there is another table called "selling_basket" that contains an id for the customer and also a foreign key for rows in item table for the items he sold and a "Customer" table that contains customers id and other informations.
suppose that i want to build an JSF page that contains a table from a view based on the "customer" table and a tree of herarichy - class
|_group1
|_item1
|_item2
-class2
|_group2
|_item3
|_group3
and when i click on a row on table customer the tree only display the herarichy for items that this customer sold just.

Answer 1

i solve the probel the description as follow :
. the problem : the problem is that when we use the tree model component with the scenario of filtration on the child nodes, we do a normal transactions of steps on the knowledge that the tree will use the master detail behavior as in table component and other ADF Master-details behaviors, so we build two view criteria one on employee and the other on department with the scenario of displaying only the department who has employees with salary equal some certain value, and only shows the employees who has salary equal that value, and on our code we apply the two criteria on the two view objects with the same value we entered to search for , the scenario works well for the top level nodes, but for child nodes it seems it doesn’t work, the behavior make us walk around our selves for why this happened. By debugging options and Tracing what SQL statements that it executes we found that the system execute two statements on the employee view object one with the bind value with the same we inserted and the other with null value, and we notice that the name of the second view object executed is not what we apply the view criteria for(departmentEO_employeeEO_emo_dept_FK_employeeView).
.The solution: we notice that the tree component doesn’t use master detail behavior as in tables, and instead of that it uses the View link assessors (the run time generated view object departmentEO_employeeEO_emo_dept_FK_employeeView ), to get the detailed items, so we should override the action of the View link assessor.
To deal with that we generate the view object rowimpl and viewimpl java classes, in the rowimpl class there is a method to call the link assessors with the following code:
public RowIterator getEmployeesView()
this.getAttributeInternal(EMPLOYEESVIEW);
We write our code:
public RowIterator getEmployeesView()
System.out.println("Here");
ViewObject s=((DepartmentsViewImpl)this.getViewObject()).getViewLinks()[0].getDestination();//we get the employee object by using the view link
// between department and employee
// then we apply the view criteria to that view object and return it as view link
System.out.println("row number "+s.getEstimatedRowCount());
ViewCriteria evc=s.getViewCriteriaManager().getViewCriteria("EmployeesViewCriteria");
s.ensureVariableManager().setVariableValue("nSal",((DepartmentsViewImpl)this.getViewObject()).getnSal());
s.applyViewCriteria(evc);
s.executeQuery();
return s;
Notice that we use the employee view object getted by the view link instead of the master details.
Regards
Mohammad.b.yaseen
Sep 26 2011 @ 11:43
J2EE Team
RealSoft
for more info this the application url :
http://www.4shared.com/file/lgeaYWXa/TreeTestApplication1.html
notice that i diidn't attach the database with the project so you can connect to the local db
Edited by: mohammad.j.b.yaseen on Sep 26, 2011 12:13 PM