Hi Again i have to thank for your help. I've even got that point. But as it still does not work as expected i started to think it over and found myself trying to check this feature on the contrib:Tree implementation.
This does not lead to the expected results :-( After all i tried it in the tacos:Tree application and everything works fine. Now there are some additional questions. Is there any good way to locate the TreeNode object that fired the listener ? In the filesystem tree demo implementation, the files path name is good enough to locate the object. I started to implement a tree containing various different TreeNode types: simple navigation, user related "domain objects", user related workflow tasks.... Therefore i have no chance to use some unique identifier. It seems to be useful if Tree maintains a key any tree node which could be used to navigate back to the TreeNode. I think about some interface for TreeNode instances that enables any node to deliver it's unique identifier - whatever this may be. And Tree(Manager) uses this information to construct a unique path based identifier. To track back to the node Tree may spit this path to elements and compare it to each visible node in the region of the tree... Mit freundlichen Gr��en, Ralf Edmund Stranzenbach -----Urspr�ngliche Nachricht----- Von: Viktor Szathmary [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 6. April 2005 15:16 An: Tapestry users Betreff: Re: Session bound state of tacos:tree / contrib:tree looking at my original mail, looks like i have mislead you: the parameter is called "state" (instead of treeState).. if that's not the problem, please send your .page/.html to the list :) viktor On Apr 6, 2005 8:06 AM, Ralf E. Stranzenbach <[EMAIL PROTECTED]> wrote: > Hi, > > thank you for this advise. I've tried this approach (and put a breakpoint on > my "getNavigationState()" method on the visit object) but i found out, that > tnis Set containing the state has been read by the tree component but does > not contain any useful state information even after changing the trees > folding mode. > > What may be wrong with my setup? > > Mit freundlichen Gr��en, > Ralf Edmund Stranzenbach > > -----Urspr�ngliche Nachricht----- > Von: Viktor Szathmary [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 5. April 2005 19:58 > An: Tapestry users > Betreff: Re: Session bound state of tacos:tree / contrib:tree > > > Hi, > > With the new tacos:Tree, this is what you need to do: add a new > property of type java.util.Set to your Visit object, and bind the > tree's "treeState" parameter to that. That's all.. > > regards, > viktor > > On Apr 5, 2005 2:01 PM, Ralf E. Stranzenbach <[EMAIL PROTECTED]> wrote: > > Hi, > > > > i would like to use either tacos:tree or contrib:tree within my Border > > component to render a representation of the applications main navigation > > menu. I like to use a tree component because some of the tree nodes may > > contain worklflow dependend tasks. > > > > So i just added the tree component within my Border but unfortunately the > > lifecycle and the inner state of the trees is bound to the page(s). > > Therefore the navigation trees on various pages render different folding > > states. > > > > Is there any chance to bind this component not to pages but to the current > > user session? > > > > Mit freundlichen Gr��en, > > Ralf Edmund Stranzenbach > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
