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 On 9/13/05, Aslak Gronflaten <[EMAIL PROTECTED]> wrote: > > Oh, > > I was not aware of this. My page caching is turned off in development, > which is where I noticed this. If it only happens once it's no > problem, and I can live with it while developing, no problem. > Regarding the state, I can see that my code differs in that it fetches > the model from a page property, while in the example there is an ognl > expression that makes a new model object: > > <binding name="contentProvider" value="new > net.sf.tacos.demo.tree.SimpleTreeContentProvider()"/> > > This object then again has its data statically initialized.... all in > all I'm slightly confused on how to convert the example to practical > use - what is the actual lifecycle of the SimpleTreeContentProvider > when it's initialized this way? > > I will try to refactor my code so I can either solve it or post a > concrete example. > > Aslak > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
