I have an application using IceFaces 3.3 (non-EE version) for user interface. I would like to replace some of the pages to PrimeFaces.
As a trivial case, I created a new page with only HTML and PrimeFaces tags on it. There is a sortable and filterable lazy dataTable on the page and nothing else. The table first loads fine but when I initiate a sorting or filtering operation, the entire table disappears.
When I inspect the page, I see IcePush is operating and the IceFaces Bridge is loaded. In case of the above mentioned partial page reload, in the response XML, the dataTable appears within delete tags however, it should be present within update tags instead.
It seems that adding org.icefaces.subtreeDiff=false to web.xml solves the problem.
Related
Persistent datatable filtering over several pages while conversation scoped bean doesn't retain (primefaces 5.1 is used) after submit (on another page) clicked and gone back to the starting screen.
I know that the possible solution should be implemneted by extending the DataTable and FilterFeature classes. Can somebody link here any solution? I can imagine this is already solved somewhere.
I have a portlet deployed in liferay 6.2 (Tomcat 7.0.42).
I use Primefaces 4 and liferay bridge 3.2.4-ga5.
I am aware of this post:
RequestContext won't work
But I have a strange problem here:
Primefaces doesn't work without the h:head tags, but when I add them the site won't update when I send the data to the bean. According to the server log the fields get updated, the p:log will say that the DOM has been updated, but nothing happens on the site, unless I remove the h:head tags. In that case the site will update with the new data, but primefaces won't work/display properly.
I even tried this demo example 1:1:
http://www.primefaces.org/showcase/ui/misc/requestContext.xhtml
But the outcome is the same.
I'm not sure what might be causing this.
Any ideas?
Thanks&BR
Edit:
Ok, I just found out, that I need to add the namespace to the update method.
So in the case of portlets it's not enough to use update("form:obj"), but update("namespace:form:obj) ... that head tag thing is still kinda strange.
try
context.update(":formId:panelId");
or
context.update(":panelId");
I am trying to make a search page using JSF, EJB, JPA & Primefaces with Pagination from an Oracle database table.
The page has two regions (1) region for entering search parameters
(2) region with a datatable showing the search result. This datatable supports pagination.
I have used standard code generated using Netbeans IDE, but dont know how to pass the parameters while clicking the search button and show the results based on the search in the datatable.
Please help me with sample code.
Thanks in advance.
For the input, just use a normal form like as you've created in a hello world tutorial. For presentation and pagination of the results, use PrimeFaces LazyDataModel. See also their showcase example.
I have a widget in my application that I need to display at two places(once in main page body and once through dialog box). Currently its code has been added twice in the page. Now I was thinking, If there was a way I could just include it only once and show the same instance in the dialog box, as in the main page body.
Can you suggest a way for this?
I'm Using:-
JSF 2.0 with Facelets
Primefaces 3.0 M3 Snapshot
JSF 2 has exactly the feature you want: it's called composite components. I bascially allows you to write a bunch of Facelet code into a file and use it just like any other JSF component, pass parameters to it, etc.
I am running JSF 2.0 and the latest version of Primefaces 2.2RC1 I believe. I am trying to create a printer friendly window. When the user clicks on a p:commandLink I want a new window to open and display a xhtml file I have named printView.xhtml.
Now I can get the window working fine using JavaScript window.open but when I open the new window it will not render any values it just displays everything as #{myBean.value}. Does anyone know how to properly open a window and extend the current scope of the application into that window so I can call all of my managed beans properly and display the values etc. etc.
it just displays everything as #{myBean.value}
So, the FacesServlet wasn't been invoked. It is the one responsible for doing the JSF works. You need to ensure that the URL in the window.open() matches the url-pattern of the FacesServlet as definied in web.xml.
If it is for example *.jsf, then you need to open it as follows:
window.open('printView.jsf');
Just an FYI, 2.2.RC1 had some bugs. You'll want version 2.2.RC2.