ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

We're using a tree in an ICEfaces 2.0 app (in 1.8 compatible mode) and want to implement lazy-loading when a node is expanded. We have followed the tree tutorials on the ICEfaces site.

The problem we are seeing is that any click on a tree node (a commandLink in the content facet) causes the last expanded or collapsed node to collapse or expand again. For example, if node two is expanded and then node four is clicked on, the click handler for node four will register, but node two will collapse as well. This action continues to repeat as other nodes are clicked.

The expand/collapse listener is an ActionListener on the tree itself which calls getNavigatedNode() and then getUserObject() on the returned node. The commandLink listener is an ActionListener that directly calls a method on the node's user object.

Has anyone else seen something like this with 2.0? I can upload some source if it would help.

I am experiencing more weird behaviour. If I contract some node, I cannot expand it again. I am using JSF 20 with IceFaces 20 in 1.8 compatible mode on GF 30.

Could this be related to ICE-1409?

gholmer wrote:

Could this be related to ICE-1409?

maybe...I am using outputText as a node contents..so it is pretty simple use case, I think.

smikesh wrote:

maybe...I am using outputText as a node contents..so it is pretty simple use case, I think.

I meant the repeating expand/contract events.

gholmer wrote:

smikesh wrote:

maybe...I am using outputText as a node contents..so it is pretty simple use case, I think.

I meant the repeating expand/contract events.

I have tried testing the Showcase application in my environment. It works correct in FF 3.6 and WebKit.

Then I tested my app in WebKit, the behaviour is quite different. When I contracting some node, as a result this node is contracted, but the other nodes (which were contracted before) are expanded. So this behaviour seems to be connected to the problem described in this bug. Maybe there is some bug in my application....I will try to see what is going on with the model when I expand/contract the nodes, but the fact that it behaves so differently in different browsers, leads me to the thought, that there are some problems in Tree component as well...