Sorry, not sure then, anyone else have an idea? -A
On Mon, Mar 15, 2010 at 6:11 AM, preeti agarwal <preetiagarwa...@gmail.com> wrote: > There are no JSTL components being used. > Though we use facelets. > > There is an entry in web.xml file : > > <context-param> > <param-name>javax.faces.STATE_SAVING_METHOD</param-name> > <param-value>client</param-value> > <!--<param-value>server</param-value>--> > </context-param> > When this entry is removed (thereby reverting to default settings), the > problem gets solved. Any reason why client side State Saving is causing an > issue? > > > > On Tue, Mar 9, 2010 at 10:23 PM, Andrew Robinson < > andrew.rw.robin...@gmail.com> wrote: > >> Do you use any JSTL tags? >> Have you any component binding in the page, especially ones that may >> live longer than one request? >> >> On Tue, Mar 9, 2010 at 7:31 AM, preeti agarwal >> <preetiagarwa...@gmail.com> wrote: >> > Description of problem : I have an xhtml page in which I use trininad >> > components (like tablelayout) and also tomahawk components (like form). I >> > have used some usual HTML components along with it. First time the page >> is >> > rendered correctly. But anysubsequent refresh causes the header to render >> > multiple times. I suspect it might have something to do with state >> saving. >> > Can anyone help me with this? >> > >> > >> > >> > >> > PS: I originally suspected that it had something to do with mixing of >> > incompatible HTML div and Trinidad components.Changing <div> to <t:div> >> > didn't solve the issue. >> > >> >
