p:dataTable is not working when ajax functionality is active

[iliTheFallen]

Hi, all...I am newbie to PrimeFaces(considering, it has not much differences than richfaces or any other component library technologies). i am trying to add a datatable to display a 2 columned html table which one of its column has text values and the other has p:commandLinks for deleting rows individually...

Code: Select all

<p:dataTable emptyMessage="" id="mailsTable" dynamic="true" value="#{mailBean.mails}" binding="#{mailBean.mailsTable}" var="mails">

                            <p:column>
                                <h:outputText value="#{mails}" />
                            </p:column>

                            <p:column>
                                <p:commandLink id="removeMail" value="Delete" process="@this"
                                               update="mailsTable" ajax="true" actionListener="#{mailBean.removeMail}"/>
                            </p:column>

                        </p:dataTable>

When i click on the "Delete" Button, my action is not fired...What might be the wrong?
Your advices are welcome ...
P.S. i am using 2.0.1 version of primefaces and i do not add "<p:resources/>" to head tag...Also i am using facelets for templating...Up till now all other components have worked fine ...
Furthermore, firebug always displays an error message which is "elTable.tBodies is undefined" and when my List<String> mails is null(or empty), datatable always displays a message as emptyMessage===>Loading...

[Oleg]

Hi,

Yes, it's not working. The problem is process="@this" attribute. I've tried with various IDs in process as well, but client IDs in partial request are very strange. The solution is - don't write process at all. Take out process="@this" and you will see it should work.

[boscooo]

Hi!

I've faced same situation of update datatable after delete/update rows.
Add a p:outputPanel enclosing the datatable and rerender it! You don't even need the process attribute.

The only thing that is strange is: when you rerender, the datatable stretches before be able to view...

[cagatay.civici]

This is not PrimeFaces related but more like standard JSF behavior, you can also experience this with f:ajax.

See: http://code.google.com/p/primefaces/iss ... ail?id=812

I've asked this to JSF expert group, waiting for response now.

[iliTheFallen]

Hi, m8s thanks for your replies...I think the problem occurs when datatable and accordion panel are nested(accordion panel-->parent, datatable-->child as you might guess)... All other combinations of components with datatable work excellent...i hope the problem will be solved in near future with primefaces' new releases...For now, i have changed accordion panel to panel...

P.S. i will be watching the thread...

[Oleg]

Hi, m8s thanks for your replies...I think the problem occurs when datatable and accordion panel are nested(accordion panel-->parent, datatable-->child as you might guess)... All other combinations of components with datatable work excellent...i hope the problem will be solved in near future with primefaces' new releases...For now, i have changed accordion panel to panel...

P.S. i will be watching the thread...

I have datatable in p:panel. It doesn't work with process defined by child in column. You can try absolute Id or relative from the next closest parent. No chance. Without process is everything fine.

[iliTheFallen]

Code: Select all

<p:panel id="mailPanel" header="#{bundle.MailGirisi}">
                        <h:form id="mailForm" prependId="false">


                            <h:panelGrid columns="1">

                                <h:panelGroup>
                                    <h:outputLabel for="mailText" >
                                        <h:outputText value="Email:"/>
                                    </h:outputLabel>
                                    <h:inputText id="mailText" value="#{mailBean.mailText}" required="true">
                                        <f:validator validatorId="mailValidator" />
                                    </h:inputText>

                                    <!-- Mesajin Update Edilmesi Lazim Aksi Takdirde Sadece DataTable Ile Ilgili Partial-Response Donuyor-->
                                    <p:commandLink id="addMail" value="Ekle" process="@this,mailText"
                                                   update="mailsTable,allMessages" async="true" actionListener="#{mailBean.addMail}"/>
                                </h:panelGroup>


                                <p:dataTable id="mailsTable" emptyMessage="Mail Giriniz" binding="#{mailBean.mailsTable}"
                                             value="#{mailBean.mails}" var="mails">
                                    <p:column>
                                        <h:outputText value="#{mails}" />
                                    </p:column>

                                    <p:column>
                                        <p:commandLink id="removeMail" value="Sil" async="true" process="@form"
                                                       update="@form" actionListener="#{mailBean.removeMail}"/>
                                    </p:column>

                                </p:dataTable>

                            </h:panelGrid>

                        </h:form>
                    </p:panel>

This works fine for me...The only problem is when you want to use p:accordionPanel with p:datatable, they cannot be nested whether there is a process attribute defined or not...I don't know may we use different versions of primefaces...I use 2.0.1 with JSF-2.0.2-FCS implementation and deploy it to glassfishv3 webcontainer...

[cagatay.civici]

Copy/Paste from my comment to the issue in tracker;

This turned out to be an implementation bug of UIData getClientId in MyFaces and Mojarra, I'll create issue
tickets in these projects related to this. For now I'll postpone this issue as fixing this in PrimeFaces side is too
big for the next release, we'll experiment after that.

These are a result of my discussion with JSF Expert Group members.

Still there is a quick tworkaround for this to use an outputpanel enclosing datatable and update that instead of
UIData.