On advice in another thread I upgraded from 2.2.M1 to 2.2RC1-SNAPSHOT.
When doing so, the update attribute in p:dataTable stops working. I use it to display detail of a record outside the table on the same page and it works very nice on 2.2.M1.
Unrelated, the xmlns:p="http://primefaces.prime.com.tr/ui" is no longer seen by the Netbeans editor. The JSF implementation does see it so the tags all get compiled but I guess there is something wrong in the TLD for the SNAPSHOT.
Regards,
p:dataTable problem in SNAPSHOT
-
- Prime
- Posts: 18616
- Joined: 05 Jan 2009, 00:21
- Location: Cybertron
- Contact:
There is no tld in 2.2.RC1 and no jsp tag classes. My NetBeans 6.9 scans the PrimeFaces facelet taglib just fine to do code completion.
update attribute is now known as onRowSelectUpdate, although I remember doing this change backward compatible so update should still be supported if I'm not mistaken.
Code from DataTableRenderer line 636;
update attribute is now known as onRowSelectUpdate, although I remember doing this change backward compatible so update should still be supported if I'm not mistaken.
Code from DataTableRenderer line 636;
Code: Select all
//update is deprecated and used for backward compatibility
String onRowSelectUpdate = table.getOnRowSelectUpdate() != null ? table.getOnRowSelectUpdate() : table.getUpdate();
If it helps here is the XHTML. This works in M1, not in SNAPSHOT. And SNAPSHOT didn't work either changing update to onRowSelectUpdate. Also, when clicking on rows the background toggles for the row but does not enforce selectionMode="single".
Looking at the browser's console, I did not get any script errors.
Looking at the browser's console, I did not get any script errors.
Code: Select all
<h:form id="llForm">
<p:dataTable
value="#{listLocations.lazyDataModel}"
lazy="true"
paginator="true"
selection="#{listLocations.selectedLocation}"
selectionMode="single"
update="llSelected"
rows="16"
var="loc"
dynamic="true"
emptyMessage="No Locations In Data Base"
loadingMessage="Loading ...."
>
<p:column sortBy="#{id}">
<f:facet name="header">
<h:outputText value="ID"/>
</f:facet>
<h:outputText value="#{loc.id}" />
</p:column>
<p:column sortBy="#{name}" filterBy="#{name}">
<f:facet name="header">
<h:outputText value="Name"/>
</f:facet>
<h:outputText value="#{loc.name}" />
</p:column>
<!-- removed some columns for brevity -->
</p:dataTable>
<h:panelGroup id="llSelected">
Selected Location: #{listLocations.selectedLocation.fullName}
</h:panelGroup>
</h:form>
Netbeans 7.1, GlassFish 3.1.1, MacOS X 10.6.8, Safari, Firefox
I was afraid you would say that. Apparently this is some sort of on-going problem with netbeans. The issue has been seen as far back as 6.5 and the issue keeps getting closed then opened again.There is no tld in 2.2.RC1 and no jsp tag classes. My NetBeans 6.9 scans the PrimeFaces facelet taglib just fine to do code completion.
http://netbeans.org/bugzilla/show_bug.cgi?id=172520
If I figure out what is going on I will post it. Annoying.
Netbeans 7.1, GlassFish 3.1.1, MacOS X 10.6.8, Safari, Firefox
-
- Prime
- Posts: 18616
- Joined: 05 Jan 2009, 00:21
- Location: Cybertron
- Contact:
Also compare with;
http://www.primefaces.org/showcase/ui/d ... nstant.jsf
Try with non-lazy as well to see if it helps;
http://www.primefaces.org/showcase/ui/d ... nstant.jsf
Try with non-lazy as well to see if it helps;
Does clearing the browsers cache help?
OK I did try all this and a few things more and no joy. But this is freaky: I downloaded a copy of the latest Firefox with the intent of debugging the browser side scripts with Firebug but didn't get the chance. Everything works in the Firefox browser! Argh!Try with non-lazy as well to see if it helps
I have three browser windows open side by side on my 27 inch iMac: Safari, Chrome, and Firefox all pointing to the same server on localhost. The same URL. The Firefox browser processes the row selections exactly as expected, the others do not. Heisenberg effect? No, I turn off Firebug and it still works.
Any suggestions?
Netbeans 7.1, GlassFish 3.1.1, MacOS X 10.6.8, Safari, Firefox
Well flying frick on a fracking cracker. That seems to fix it.Is it because <f:view contentType="text/html"> is missing on the page
I think this note needs to be added to the User's back in Chapter 2. Notice the "Hello World" starter doesn't have <f:view> in it.
It turns out that I have run into this before, with gmaps4jsf library which has the same issue. That should have made me alert to this. What happens is that the browsers render either an HTML DOM or a XML DOM depending on the content of the page. It looks like some of primefaces but not all of it depends on the objects that show up by default in the HTML DOM but not XML DOM. I guess Firefox implements a workaround for this.
Thanks everyone for all the attention.
Netbeans 7.1, GlassFish 3.1.1, MacOS X 10.6.8, Safari, Firefox
-
- Information
-
Who is online
Users browsing this forum: No registered users and 5 guests