I am using the Tacos Tree component in Tapestry. I solved the problem of the
ROOT not being static by having Tapestry keep the object in an Application
State object (via Hivemind).
However, now I find that I cannot get the tree to expand because I am not
accumulating the Set of keys that should keep track of which nodes are open.
I suspect that, again, Tapestry should be keeping that state in the
Application State object (via Hivemind).
Is that correct?
Is there any example of how that state should be managed? I am having a hard
time understanding exactly how to manage that. I have implemented the
tacos4-beta2 and have that source but I would be especially grateful for any
suggestions or pointers on how that state should be managed. With all the
abstract methods in Tapestry, the usual "read the source" approach is
dead-ended.
I would welcome any suggestions and--please--forgive me in advance if I'm
asking any dumb questions. I'm a newbie to Tapestry and Tacos and I don't want
to annoy the pioneers.
Thank you,
Ty
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel
