The code for the lazy loading method is very complicated in my app. I use java code to call an application that gets the nodes through a VB interface from an Application written in C++.
I think the problem is not the lazy loading itself but the treewalker.next() or the HTMLTreeRenderer Anyway, thanks for your help, I just want to know if there are people here that have seen errors like that with their implementations. The problem is that if users are clicking very fast, without waiting util one node has opened, the renderer hangs (not my lazy loading). So it looks for me that in the treewalker, there are some variables manipulated by other threads or something, but I made everything synchronized. -----Ursprüngliche Nachricht----- Von: Andrew Robinson [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 25. März 2008 14:01 An: MyFaces Discussion Betreff: Re: Lazy loading tree is crashed by fast clicking users That didn't clarify anything at all. Please show us code, we are not mind readers :) On 3/25/08, Martin Schlierf <[EMAIL PROTECTED]> wrote: > Hello, I wrote my own tree nodes. > In the getChildren() method I load the child nodes from the file system. > The methods for loading the child nodes are all synchronized... > > -----Ursprüngliche Nachricht----- > Von: Andrew Robinson [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 20. März 2008 16:27 > An: MyFaces Discussion > Betreff: Re: Lazy loading tree is crashed by fast clicking users > > How are you lazy loading the tree2. There is no built in support for > it, so your problem is completely dependent on your implementation of > it. > > On Thu, Mar 20, 2008 at 6:00 AM, Martin Schlierf <[EMAIL PROTECTED]> > wrote: > > > > > > > > > > Hi, > > > > I'm facing problems with a lazy loading Tree2. > > > > My nodes load data from the file system to get its children in the tree. > > This takes some seconds to load. > > > > > > > > For example the user gets the root node which has 5 child nodes. > > > > If the user clicks on all 5 plus signs to open the nodes the renderer > never > > finishes. If the user just clicks one node and waits it is no problem. > > > > > > > > It may be that my implementation of the nodes has error but I cannot find > > them. > > > > > > > > Has anyone seen such problems with a own lazy loading node tree structure? > > > > > > > > Thanks, Martin > > > > > >
