I forgot to mention - if you want to use facelets.BUILD_BEFORE_RESTORE you currently have to be aware of 2 things:
1. there is a bug in facelets which breaks state-saving when this param is on you can work around that by either patching facelets or using a custom state manager 2. you cannot modify the component tree manually since it breaks state saving in this case regards Ernst On 5/20/08, Ernst Fastl <[EMAIL PROTECTED]> wrote: > the problem here is that html as well as f:verbatim results in transient > compoents which are not available after restore view anymore. > In the facelets 1.1.14 there is a parameter to enable build of the > tree before restore: > > <context-param> > <param-name>facelets.BUILD_BEFORE_RESTORE</param-name> > <param-value>true</param-value> > </context-param> > > with that parameter it works in my case > > cheers > > Ernst > > > > On 5/20/08, Werner Punz <[EMAIL PROTECTED]> wrote: >> Guy Bashan schrieb: >>> Thanks Warner, >>> This is quite a big limitation ... ;-) >>> Do you know if ajax4jsf solves this issue? >>> >> They do it on the servlet filter level by cutting and altering the html >> code... >> >> Tomahawk ppr does it on the component tree level to my knowledge. >> Don´t know how Trinidad does it, but I assume they do it on the Tree >> level as well. >> >> One way or the other you have to intercept to get such mechanisms in >> place. >> >> >
