Hi again, I finally found the problem - don't know if one should call it a gotcha... Thing is the data for the getChildren method of my ITreeContentProvider was returning a Set from a hibernate mapped association. The set is not ordered, and this caused the problem. As soon as I changed it to a list, the tree worked beautifully. Since the documentation doesn't mention it, and the method signature says getChildren can return a Collection, it wasn't exactly obvious. (except for in hindsight)
Aslak On 9/13/05, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > To be fair, there were a number of bugs that I added to Tree over the course > of alpha-1 through alpha-2, but as far as I know all have been fixed as of > this last release. > > The contentProvider parameter doesn't have any special semantics other than > the normal tapestry binding semantics. You could link and chain the > contentProvider parameter from another component if you wanted to as well > (which I what I'm doing with the tree) . > > If you show me a snippet of code I can help, but as far as I know there > aren't any gotchas as of alpha-3. > > jesse --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
