Re: rendered question

[Mike Kienenberger <mk...@gmail.com>]

You should reply to the mailing list and not to individuals.

For what it's worth, I've never had to move the t:saveState into the
html header.   It's always worked fine in the html body for me.   The
problem probably lies elsewhere.


On 12/22/06, support <ap...@purpleblade.net> wrote:
> yes, I am sure.  There is no validation/conversion error.  It is request
> scoped.  I am using t:saveState but that does not seem to be working.  I
> went back and the problem was that the saveState line was not in the
> header. It was outside the header tag but was not complaining so assumed
> it worked.  It is working now.  This told me where to look for the
> problem.  spent several unproductive hours pouring over things and
> trying things.
>
> Thanks
>
> Roger
> ---
> The other common situation is that your rendering condition is based
> on request-scoped data.
>
> The rendering condition value must remain constant between the
> response when the button is rendered, and the next request when the
> button is processes.
>
> Ie, if <uicommand rendered="#{bean.condition}">, then bean.condition
> must not be request-scoped.  (it can be session or application scoped,
> or it can be preserved to the next request using t:saveState or
> something similar.  It can even be recomputed each request so long as
> the computation returns the same value on the following request).
> ---
> Are you sure there is no validation/conversion error?
>
> This is the most frequently reason fo not invoking actions.
>
> add a h:messages tag to you page ensure this.
>
> Regards,
>  Volker
>
> --- original
> I have a command link that is only rendered if a property is set in the
> back end bean.  When I click the button it is supposed to add a row to a
> database.  When the page is first rendered the [Add] button appears, I
> enter info into the inputText boxes and click [Add] and the information
> gets inserted, however when the page returns, a second add does not work.
>
> When the [Add] button is clicked, it never hits the backend bean at
> all.  I am quite sure of this.  The commandlink has a rendered tag that
> determines if the commandlink & img is rendered at all.
>
> Is there any reason it would work the first time but not the second time?
>
> Thanks
>
> Roger
>
>