The 2.x Tree does not handle IPEs. The 3.0 Tree won't either, but by using the ADG's hierarchicalCollections and some glue, it should work. I'll be blogging on how to do that right after 3.0 goes out the door or sooner if I get a chance.
You might be able to workaround some of the issues in 2.x. There are two kinds of IPE issues with the 2.x tree. It expects at least one page of the top level of the hierarchy to be paged in and ready to go. That should get you past some of the errors. Next, it does not expect the lower levels of the hierarchy to be paged. You can workaround that by returning a zero-length children collection via a custom ITreeDataDescriptor until the actual data arrives. One clever person stuck in one entry that said "fetching children..." until the children arrived. You will get best results in 2.x if the entire top-level is paged in, and you use the zero-length or single entry trick until the children are paged in. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Sent: Friday, January 04, 2008 2:15 PM To: [email protected] Subject: [flexcoders] Lazy Loading on Tree Component with LCDS We are having trouble with lazy loading and the tree component. We get item pending errors all over the place. Is this to be expected or should the tree component handle lazy loading like the DataGrid? We are using LCDS with Hibernate so the calls are made internally. If not, what is the proper way to handle Item Pending errors. Thanks for the info. - Kevin
