Comments on: Dropping trees

By: Luc Bors

Luc Bors — Thu, 14 Jan 2010 08:06:41 +0000

Hi Rohit,
I’ve just uploaded an ADF 11.1.1.2 workspace. You can find the link to this workspace at the bottom of this post.

By: Rohit

Rohit — Mon, 04 Jan 2010 12:58:45 +0000

Where do I get the source code from ?

By: J Developer

J Developer — Thu, 29 Oct 2009 13:40:51 +0000

To reply to myself, after a lot of pains… exception happens because of DisplayRow=selected, so _do_not set this property for af:treeTable when you doing drag-and-drop…

By: J Developer

J Developer — Wed, 28 Oct 2009 18:50:48 +0000

Hi,
Excellent example.
As I can see, this is the two-level af:tree. Did you tried to do the same with multi-level ( > 2) af:treeTable ?
Whatever I do, I am stucking with :

java.lang.NullPointerException
at oracle.adfinternal.view.faces.model.binding.RowDataManager.getRowIndex(RowDataManager.java:189)

- Can you post some example regarding drag-and-drop in the multilevel af:treeTable ?

By: Dom

Dom — Fri, 12 Jun 2009 09:48:55 +0000

Hi,

There is a bug I believe in the af:tree in 11g in that if you have >2 levelsit does notrender properly. I have created a tree using view objects and 2 view links in between (thus creating a 3 level hierarchy) and when I try to drill down to the 3rd level the expand node icon just flashes when I try to drill down. Have you experienced this and if so I would be very interested in hearing how to work around it – I have curently got it logged as an official bug in Metalink.

thanks

By: Ansar

Ansar — Wed, 20 Aug 2008 06:12:34 +0000

Hi Luc, This is a great functionality and well explained. How do i achieve this same functionality using Toplink. Thanks ansar

By: Luc Bors

Luc Bors — Mon, 14 Jul 2008 13:41:47 +0000

I agree that this should be possible through the binding layer.

However, the treeBindingEditor only creates the iteratorBinding for the highest node. In this case the department node. All of the attributes that are present in the tree node defs will be shown in the tree. I don’t want to show the departmentId of the employee in the tree, so I cannot create an attribute binding for that.

Default, there are no usable bindings available to update the departmentId of the employee.

Therefor I think that it’s not straigthforward to handle all this via the binding layer.

By: Frank Nimphius

Frank Nimphius — Mon, 14 Jul 2008 08:14:26 +0000

Hi,

why do you use the access to the EO to update the model ?

EmpDeptServiceImpl am = getAm();
EmployeesViewRowImpl empRow =
(EmployeesViewRowImpl)am.getEmployeesView1().getRow(empKey);
empRow.setDepartmentId(departmentNew);
am.getDBTransaction().commit();
// requery the employees view
am.getDepartmentsView1().clearCache();
am.getDepartmentsView1().executeQuery();

This can be doen through the binding layer entirely and also would allow you to submit the change for a later commit

Frank

By: Lucas Jellema

Lucas Jellema — Fri, 11 Jul 2008 09:05:26 +0000

Hi Luc,

: very nice article. great functionality, very well explained and with the occasional tongue-in-cheek thrown in that makes it a nice read as well. Cool stuff, 11g! You make it seem very simple.

best regards, Lucas

By: Edwin Biemond

Edwin Biemond — Thu, 10 Jul 2008 22:17:12 +0000

Very nice, I will bookmark this entry. I got it working in Flex but not in jdev 11g. Please make some more cool dnd samples.