Primefaces 5.2 bug

[Grantsmith]

This code works in 5.1, but not 5.2. In 5.2 the project object returned is always null.

Code: Select all

<p:dataTable id="data" var="project" value="#{projectList.projectDataModel}" scrollable="true" scrollHeight="555" resizableColumns="true"
                         selection="#{projectList.selectedProject}" selectionMode="single" filteredValue="#{projectList.filteredProjects}">

                <p:ajax event="rowSelect" listener="#{projectList.onRowSelect}"
                        update=":form:growl :nav"
                        oncomplete="editRowCommand()" immediate="true"/>

Code: Select all

public void onRowSelect(SelectEvent event) {

        Project project = (Project) event.getObject();
...

[mert.sincan]

I tested but I didn't see this bug. Please try Select Events example in showcase (Running PrimeFaces-5.2); http://www.primefaces.org/showcase/ui/d ... tion.xhtml

[kurtomerfaruk]

GrantSmith join you

PrimeFaces 5.1 running but 5.2 not running

when i click select datatable below throw error
getrowdata(string rowkey) must be implemented when basic rowkey algorithm is not used.

[kukeltje]

Search the forum. Has been discussed several times the last couple of weeks

[Grantsmith]

Search the forum. Has been discussed several times the last couple of weeks

Yet a search for +dataTable +select +5.2 does not show any such discussion ? Am I missing something here ? I can see that the Demo code works, but this doesn't help me understand what has changed which breaks MY code. I see one discussion about implementing rowKey, but that doesn't apply in my case.

I will continue experimenting until I find what underlying minuscule detail known only to the gods of Primefaces may be causing this. In the words of Dr Evil: "Throw me a freakin bone, people !"

[Grantsmith]

After wasting a couple of hours, I have found the problem, which I still consider a Primefaces 5.2 bug.

Even though my DataModel implements getRowKey and getRowData, you STILL have to specify rowKey="#{project.id}" in the p:dataTable. This was NOT required in 5.1.

I can understand why this has changed. With using rowKey directly in the tag, you now don't HAVE to implement a SelectableDataModel in the backing bean, because you can specify the rowKey; so you can simply use a List. That is all very cool, but when the user HAS a SelectableDataModel implemented, Primefaces should recognize that and allow the old behavior.

[tandraschko]

Please create a issue + attach a minimal bean and xhtml example. Would be great if you could build it based on showcase beans/xhtml

[fpoulet]

I confirm that we have exactly the same issue.
Actually it prevent us to move to 5.2
Waiting the first elite with a fix.

Regards,

[AHesse]

Datable selection is broken in our app when using PF 5.2. This is a showstoppper for us too. Specifying the rowkey does help, but we got performance issue with huge multiple selections. Does an issue already exist?

[kukeltje]

I have no perfornance issues with multiple selection. Please create a new topic, post code and profiling info