I'm using JSF 1.2 on IE11. Recently I added Richfaces api - 3.3.3, Richfaces impl- 3.3.3, Richfaces ui - 3.3.3 , in order to solve the issues I've been getting while migrating from IE 8 to IE 11. After these jars were added, I've been getting issues with the reRender.
Scenario is, a selectonemenu change event triggers is supposed to render another a4j outputPanel panel. But this only happens after a refresh(pressing F5).
Without these jars, my project seems to be working fine, except the IE 11 compatibility issues.
RichFaces 3 does not support IE9 (refer here for more details). And likely does not support IE10+.
You can test it out on demo environment. If it does not work your options are to upgrade JSF/RF or add IE compatibility headers.
Related
The scenario is a mobile page developed with JSF and Primeface Mobile. I want to navigate in the same xhtml page between multiple pages (have a look at: JSF Primefaces Mobile navigation). After upgrading PrimeFaces from version 6.1 to 7.0 org.primefaces.mobile.application.MobileNavigationHandler does NOT exist anymore. What do i need to use instead? The migration guide "6.2 to 7.0" (https://github.com/primefaces/primefaces/wiki/Migration-Guide) doesnt help me: "[...] Mobile has been removed in favor of responsive features. [...]"
There is NO migration path for you other than rewriting your code.
PrimeFaces Mobile was completely removed in 7.0
See this blog post from Primefaces: https://www.primefaces.org/primefaces-6-2-roadmap/
PF Mobile is a renderkit for the existing components however we’ve
just realized that we have to maintain two different sets at the same
time so decided to deprecate PF Mobile and focus on the responsiveness
of the standard renderkit. So in 6.2, mobile will be deprecated and
removed in 7.0.
Have a look at my migrated fork: https://github.com/djmj/primefaces-mobile.
I extracted the mobile components from PrimeFaces 6.1 and adapted them to PrimeFaces 7.0 as a separate library. I did testing with mobile showcase and will test it in our own application and production the next days.
My application was working on JSF 2.2 and Primefaces 6. Application server Glassfish 4.1. I have been succesfully using Primefaces file upload initially. I have upgraded my Glassfish 4.2 and Netbeans 8.2. Now fileupload xhtml is not calling managedbean. The fileupload mechanism has stopped working and no error is thrown, The upload scroll bar moves and completes but the managedbean is not called. I am not clear what could be the issue. Is there a way to debug such issue. To me it seems that http response is not working properly but not able to
capture it. Please suggest some test which i can try to debug.
Fileupload does not work with Primefaces 6.0 and JSF 2.3.
You have 2 options:
Replace the javax.faces.jar file in glassfish\modules\ with mojarra 2.2.8-21 http://central.maven.org/maven2/com/sun/faces/jsf-api/2.2.8-21/jsf-api-2.2.8-21.jar
Update primefaces to version 6.1
The bug was fixed already:
https://github.com/primefaces/primefaces/issues/2121
I have a web mobile application running on JBoss 7.1.1 AS, Mojarra JSF 2.1, Primefaces 3.5 and Primefaces Mobile 0.9.4.
Primefaces 4 was released for community. I updated it and the application crashed when using p:dataList.
Anyone knows if primefaces 4 supports primefaces mobile 0.9.4?
Thanks.
It's not supported. Have a look at this blog (http://blog.primefaces.org/?p=2894) and scroll to the comment by srbala. Not sure when mobile 1 is coming out. I'm waiting for it.
Can RichFaces (either 3.x or 4.x) and PrimeFaces (either 3.5 or 4.0) be used in the same JSF 2.x application? Will they coexist nicely?
My goal is migrating from RichFaces 3.x to PrimeFaces. I would like to start by using PrimeFaces for a new submodule of my web application, and eventually migrate everything.
It would be fairly easy to set up a simple hello-world sized project and try it out; I am asking here because I wish to know if there are some problems when doing this on real-life sized projects.
I have a problem with WebSphere 6.1 and Primefaces. I have created an application, but used a local Tomcat appserver for testing. Everything was working fine, until I tried to deploy it on WAS 6.1.
After investigating the internal server problem, I saw, that WAS 6.1 only supports JSF 1.1, so I can throw out the whole interface :S
My question is, what is the best and most importantly, the fastest solution for this:
my interface is very simple, only panels, commandbuttons, a menu and a printer component. Is it possible to go back to a previous version of primefaces that supports jsf 1.1 keeping most of the code? (as I read, primefaces 1.1 is the last, which is far away from 3.5 )
use another faces implementation, if yes which one is the easiest to switch to from primefaces
can WAS 6.1 be made somehow compatible with JSF 2?
any other way
It's possible if you drop the necessary JSF 2.0/2.1 + PrimeFaces 3.5 JARs in webapp's /WEB-INF/lib and set in WebSphere admin the classloader policy to PARENT_LAST on both the EAR and WAR. This will force WebSphere to load webapp-bundled JSF instead of its own bundled JSF.