Thanks Venktra, My colleague tells me they have tried progmatically clearing the selectedRowKeys and disclosedRowKeys in the backing bean with no success, the selected state is persisted and the tree remains expanded. Removing the context-pararm has had the desired effect I just cant find any decent documentation around org.apache.myfaces.trinidad.CHANGE_PERSISTENCE.
Regards Andy ________________________________ From: venkata guddanti [mailto:[EMAIL PROTECTED] Sent: 03 October 2007 17:38 To: MyFaces Discussion Subject: Re: [Trinidad] request backed TreeTable Hi Andrew, I believe this may not have anything to do with change persistence. The selection and the expansion state is part for the component state (SaveState, RestoreState). One possibility is that you use a request scoped bean to bind the selectedRowKeys and disclosedRowKeys attributes via EL. Regards, Venkata On 10/2/07, Andrew Richards <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: Ive found the answer, The following context param was set in the web.xml <context-param> <param-name>org.apache.myfaces.trinidad.CHANGE_PERSISTENCE</param-name> <param-value>session</param-value> </context-param> I cant find org.apache.myfaces.trinidad.CHANGE_PERSISTENCE in the documentation, there is nothing under web.xml in the dev guide(http://myfaces.apache.org/trinidad/devguide/configuration.html#web.xml ) Does anyone know here this is documented so I can determine the effect of removing this will have on my application? I guess this has been set for a reason :-) Thanks, Andy -----Original Message----- From: Andrew Richards [mailto:[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>] Sent: 02 October 2007 11:09 To: MyFaces Discussion Subject: [Trinidad] request backed TreeTable Hi, I have a Trinidad TreeTable displaying my hierarchy of selectable data which works fine. The problem I having is that when I user selects a row in the table and then navigates away from the page and the returns to the page, the treeTable selection is persisted and the row is expanded and selected? My backing bean is request scoped, which confuses me? Does anyone know how I can force the TreeTable to return to its original state on every new request? Many thanks, Andy
