Hi, I know Trinidad components use a special way of client side state saving. Maybe the problem is that the Tomahawk components do not support this Trinidad-specific solution. So it could be related to the fact that you're mixing Tomahawk and Trinidad components, as you suggested.
Why are you mixing Tomahawk and Trinidad components? Apart from some special cases (e.g. captcha and schedule) there are Trinidad alternatives to every Tomahawk component. So why don't you whitch to Trinidad-only? An alternative solution would be to turn off Trinidad's special client side state saving method. (See [1]) But my advise is to do not mix Tomahawk with Trinidad. Best regards, Bart Kummel [1] http://myfaces.apache.org/trinidad/devguide/configuration.html#org.apache.myfaces.trinidad.CLIENT_STATE_METHOD ___________________________________________________________ Author of the book "Apache MyFaces 1.2 Web Application Development" See http://tinyurl.com/am12wad On Tue, Mar 16, 2010 at 06:37, preeti agarwal <preetiagarwa...@gmail.com>wrote: > Can anyone help in this issue? > > > On Mon, Mar 15, 2010 at 9:56 PM, Andrew Robinson < > andrew.rw.robin...@gmail.com> wrote: > > > 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. > > >> > > > >> > > > > > >
