is called in spite of rendered=false

Asked Mar 05 '21 at 15:54

Active Mar 06 '21 at 14:26

Viewed 71 times

I am wondering about the following behaviour of <p:dataTable filteredValue>. Hopefully you can explain it and tell me how to avoid it.

The backing bean method is called even though the corresponding component is not rendered.

<p:panel rendered="#{false}">
    <p:dataTable ... filteredValue="#{backingBean.filteredRowModels}">
        ...
    </p:dataTable>
</p:panel>

Do you know how avoid calling the backing bean method if it is not rendered?

edited Mar 06 '21 at 14:26

Jasper de Vries

asked Mar 05 '21 at 15:54

Just put a debug breakpoint and inspect the call stack as usual in order to figure out why the line of code is called. – BalusC Mar 05 '21 at 16:39
The init Method is called during DataBaseTable.getFilteredValue. As mentioned before, the corresponding DataTable is not rendered. Does JSF process Component even thou there are not rendered? – Manuel Drieschmanns Mar 05 '21 at 19:03
Excellent. I've fixed your question. The original question was way too blurred. I'd say this is in the end just a bug/oversight in PrimeFaces. Report issue and in the meanwhile patch the renderer. – BalusC Mar 06 '21 at 10:49
What version of PrimeFaces are you using? Filtering was overhauled in PF 10, did you try with that version? – Jasper de Vries Mar 06 '21 at 14:25
We are using Primefaces 8.0 – Manuel Drieschmanns Mar 06 '21 at 16:36
As a workaround, I replaced the rendered attribute with a c:if tag to prevent Primefaces from initialising the bean. – Manuel Drieschmanns Mar 06 '21 at 17:01
Can you please try with 10 to see if an issue needs to be reported? – Jasper de Vries Mar 08 '21 at 09:29

0 Answers0