Conceptionally, it probably makes the most sense to stick your
x:saveState components at the top, right after your f:view. It
doesn't really matter where you put them, but the state always gets
restored in the restore view phase and this always happens before the
apply value phase (where all of the values get assigned from your
other components get assigned). The ordering of your x:saveState
components won't affect anything but your other x:saveState
components.
On 9/19/05, Mathias Brökelmann <[EMAIL PROTECTED]> wrote:
> You can not put x:savestate inside a column. The state of the nested
> columns components is not saved for each row.
>
> 2005/9/19, Christian Froelich <[EMAIL PROTECTED]>:
> > Hello,
> >
> > I tried to save foo and only foo with x:saveState but it's
> > not working.... the action method is NOT CALLED.
> >
> > now my jsp looks like that:
> >
> > <h:column id="columnBrowsTab1" rendered="#{foo.secondBoolean}">
> > <x:saveState id="foo" value="#{foo}"/>
> >
> > <h:commandLink action="#{listener.sort}"
> > value="#{listener.browserHeadList[1]}"
> > rendered="#{foo.obid == 'obid'}" >
> > <f:param id="sortBy" name="sortBy"
> > value="#{listener.browserHeadList[1]}"></f:param>
> > <f:param id="colNr" name="colNr" value="'1'"></f:param>
> > </h:commandLink>
> >
> > <h:outputText value="#{foo.secondColumn}"
> > rendered="#{foo.obid != 'obid' and !(foo.obid == listener.obid)}"/>
> > <h:outputText value="#{foo.secondColumn}"
> > rendered="#{(foo.obid == listener.obid)}"
> > styleClass="treeNodeSelected"/>
> > </h:column>
> >
> > I would be glad if anyone could give me another hint!
> >
> > Warm Regards,
> >
> > Christian
> >
> > --
> > Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko!
> > Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner
> >
>
>
> --
> Mathias
>
