hey,
Is it possible that when we explicitly removed the mention of state saving
mechanism from web.xml configuration; that every component library is
choosing its own default rather and that could be causing things correctly?
here is my take at it:
1. state saving configured to client-- Trinidad components work fine but
some tomahawk components have isssues
2. state saving configured to server-- Tomahawk components and JSF RI
components work correctly, but some trinidad
componetns show some issues.
3. state saving method explicitly removed so that each component library
picks up its own default mechanism for saving and restoring the
component's state; thus harmoniously ork with each other with out any issues
I'm just guessing but it would be better if this analysis I put forward in
the above three points holds true for any JSF librar, so that developers can
build pages and applications with the best components available in the
market; (OSS or proprietary).
Regards,
Samba
On Mon, Mar 15, 2010 at 9:56 PM, Andrew Robinson <
[email protected]> wrote:
> Sorry, not sure then, anyone else have an idea?
>
> -A
>
> On Mon, Mar 15, 2010 at 6:11 AM, preeti agarwal
> <[email protected]> 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 <
> > [email protected]> 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
> >> <[email protected]> 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.
> >> >
> >>
> >
>
