With firebug i have found, that the difference.
<td class="dr-tree-h-text rich-tree-node-text" id="j_id4:j_id50:portTreePaneId:j__id51:0:j__id55:0:j__id59:0::j_id60:text"
<td class="dr-tree-h-text rich-tree-node-text" id="j_id4:j_id50:portTreePaneId:j__id51:0:j__id55:0:j__id59:0::_defaultNodeFace:text"
I don't understand, what is the _defaultNodeFace? Anybody can help me? Thanks in advance!!
the attribute: toggledonClick of rich:tree works fine without the a4j:dropsupport of the treeNode, otherwise get the error message.
If wrapted the treenode with an a4j:outputPanel can avoid the error, and the execute somewhat quickly. But get the new problem:
If the treeNode is wrapted with a4j:outputPanel, the label of tree node can not be correctly shown. the shown label format: java package@objectId.
_defaultNodeFace is the implicit instance of rich:treeNode that is constructed if you have no suitable rich:treeNode as immediate children of rich:tree. You should not wrap rich:treeNode into a4j:support.
You should not wrap rich:treeNode into a4j:support
Hi Nick, do you mean a4j:support or a4j:outputPanel?
Sorry, I meant to say a4j:outputPanel.
Thank nbelaevski for your reply. I have understand.
Without the a4j:outputPanel wrapted with treenode, which with the a4j:dropsupport, i get always the error message by on collapse the treenode.
drop. Element with [j_id4:j_id50:porttreePaneId:j_id51:0:j_id55:0:j_id59:1::j_id60]ID was not found in the Dom tree. Probably element has no client ID or client ID hasn't been written. DnD's disabled. Check please.
If use the toggledonClick, either without the a4j:dropsupport, or wrapted the treenode into the an a4j:outputPanel( Nick had negatived it).
Is it a bug? or can i workaround? It is ineffectively, if the a4j:dropsupport is wrapted into an a4j:outputPanel.
I've seen this error using dnd components inside treeNode. And avoid tham on my side with just removing the dnd components and using built-in tree dnd functionality.. Maybe its the case for you?
I must use the D&D inner tree, so i have to avoid the toggledOnclick. Anyway thank you again.