Some model behind the tree component is necessary; either fully programmatical (built with TreeNode classes) or defined declaratively in the view (by using *treeNodeAdaptor tags).
Hi Thanks for your reply.
We have a situation where a backing bean becomes very awkward, because the onclick and drag and drop behaviours are different depending on the "item" we put in the tree (the tree items are not the same type) and writing and adapter would be fiddly.
Perhaps we should be using a different structure I'm not sure. This is for a menu that we want to be able to drag and drop items onto - so I thought tree would be a good structure.