-
1. Re: rich:tree state
bobbiee Feb 18, 2008 12:49 PM (in response to bobbiee)I found out. Its only to assign componentState attribute with value from backing bean, then it works.
I have another thing to wonder about. My page is divided into 2 parts. First part contains rich:tree, content of the second part depends on which node is clicked from tree. I am thinking about how to render (on click in tree) only this second part (without rendering whole page). Cant use a4j:include, cause I dont want tree to be rerendered.
Any sugestions? -
2. Re: rich:tree state
venkat.sadasivam Feb 21, 2008 10:24 AM (in response to bobbiee)Hi Lukas,
I too have same problem in preserving tree state. Should I have to pass tree node id for the attribute componentState?
Please guide me.
Thanks,
Venkat -
3. Re: rich:tree state
bobbiee Feb 21, 2008 6:26 PM (in response to bobbiee)Hi Venkat,
which switch do you use for your tree?? -
4. Re: rich:tree state
venkat.sadasivam Feb 21, 2008 10:31 PM (in response to bobbiee)Hi Lukas,
I use "client" switch. When a leaf node is selected I reload the whole page.
thanks,
Venkat -
5. Re: rich:tree state
bobbiee Feb 22, 2008 8:59 AM (in response to bobbiee)So your problem is that when you change view by clicking tree node, you reload whole page? Look inside your faces-config.xml file and delete all navigation rules inside there. This is the cause of the "ajax request cause non-ajax request" and reloads whole page.
-
6. Re: rich:tree state
venkat.sadasivam Feb 26, 2008 11:23 PM (in response to bobbiee)I resolved this issue by keeping TreeState in the session scope.