Alex Burton wrote:
You could set up the backing bean to be in the session scope so that
the TreeModelBase doesn't have to be created each time. You just have
to update the model then if there is a change to it.
Thanks.
Adam
cheers,
alex.
On 18/01/06, Adam <[EMAIL PROTECTED]> wrote:
Dear All,
I have some code which if you like I'll post here which basically
renders out any XML file via an underlying JDOM DOM object using tree2.
The problem is that every time I click on a tree element (i.e. a node)
it would appear that the entire visible tree is repocessed & thus if I
have a reasonably large XML document it has to go through lots of jdom
elements etc again & again & again.
Is the tree cached in some way such that only the children of the newly
expanded node need be processed rather than every visible node & their
children?
e.g. if I have a document which has say 10 children hung off the root,
every time I click on an element I see the same 10 root elements being
re-processed & then their children etc.
Adam
