I had the same problem as described in the question. That’s why I came up with the following solution: Include the primefaces built-in jQuery library (currently 1.4.1) as including an own jQuery library leads to CSS formatting problems. Adding the target=”head” attribute allows for specifying the tag everywhere – e.g. when using templating you not … Read more
PF is a Javascript function. In Primefaces 4.0 the Javascript scope of widgets changed. Prior to version 4.0 you could open a dialog widget with widgetVar.show();. In Primefaces 4.0 and above the widgets are stored in a Javascript widget array. When you call PF(‘widgetVar’) it is looking for the widget in the array and returning … Read more
I understand that you want to filter based on the name input field. The <p:commandButton> sends by default an ajax request and has a process attribute wherein you can specify which components you’d like to process during the submit. In your particular case, you should then process only the name input field and the current … Read more
The PrimeFaces ajax events sometimes are very poorly documented, so in most cases you must go to the source code and check yourself. p:selectOneMenu supports change event: <p:selectOneMenu ..> <p:ajax event=”change” update=”msgtext” listener=”#{post.subjectSelectionChanged}” /> <!–…–> </p:selectOneMenu> which triggers listener with AjaxBehaviorEvent as argument in signature: public void subjectSelectionChanged(final AjaxBehaviorEvent event) {…}
just add this attribute rowKey to the datatable tag : <p:dataTable border=”1″ value=”#{projectAdminisrationMB.projectNoUsersList}” var=”userObj” rowKey=”#{userObj.name}”selection=”#{projectAdminisrationMB.selectedUsers}” selectionMode=”multiple” rowIndexVar=”rowIndex” binding=”#{table2}”>
The rowEdit and cellEdit events does by design inside the table not update/re-render anything else than the current row, even not when explicitly specified in update attribute. It’s the consequence of PrimeFaces’ a bit overzealous attempt to minimize the response size. This makes sense in most of the cases, but not in specifically your case. … Read more
It failed because you used ajax=”false”. This fires a full synchronous request which in turn causes a full page reload, causing the oncomplete to be never fired (note that all other ajax-related attributes like process, onstart, onsuccess, onerror and update are also never fired). That it worked when you removed actionListener is also impossible. It … Read more
Preface: I don’t work with JSF, but there are a couple of things that might steer you back to where you want to be: a) when working with just the date portion of a dateTime in a standard calendar, consider using: someCalendar.set(Calendar.MILLISECOND, 0) b) consider using joda-time, as it seems to be frequently recommended (here, … Read more
<p:commandButton> needs one of the following to work correctly: the update attribute to list id’s of components to re-render (for AJAX requests) the attribute ajax=”false” to make a normal, non-ajax submit. If you have neither, the button does per default an AJAX request with no UI feedback. Additionally, I’ve had problems with neither option working … Read more
In PrimeFaces 3.0, that style get applied on the generated inner <div> of the table cell, not on the <td> as you (and I) would expect. The following example should work out for you: <p:dataTable styleClass=”myTable”> with .myTable td:nth-child(1) { width: 20px; } In PrimeFaces 3.5 and above, it should work exactly the way you … Read more