Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
FileUpload is broken in PrimeFaces 6.2
Please see my post and the answer on the Primefaces forum:
https://forum.primefaces.org/viewtopic.php?f=3&t=55473&sid=feae78bc8d87a9cc682c85df0b501c8d
We are working with Liferay Community Edition Portal 7.0.3 GA4 (Wilberforce / Build 7003 / June 19, 2017)
Is it possible that the newest Liferay Faces Bridge (4.1.0) is not compatible with Primefaces 6.2.0?
Thank you!
https://forum.primefaces.org/viewtopic.php?f=3&t=55473&sid=feae78bc8d87a9cc682c85df0b501c8d
We are working with Liferay Community Edition Portal 7.0.3 GA4 (Wilberforce / Build 7003 / June 19, 2017)
Is it possible that the newest Liferay Faces Bridge (4.1.0) is not compatible with Primefaces 6.2.0?
Thank you!
Kyle Joseph Stiemann, modified 7 Years ago.
Liferay Master
Posts: 760
Join Date: 1/14/13
Recent Posts
Hi József,
PrimeFaces 6.2 is not compatible with Bridge Impl 4.1.0. We already have made the necessary changes:
- https://github.com/liferay/liferay-faces-bridge-impl/commit/fdd3ac7556a0390f6f5f96d64f430cca7cd14451
- https://github.com/liferay/liferay-faces-bridge-impl/commit/ce36086b94afb4c50f514b83cc9a061ead188704
You can try Bridge Impl 4.1.1-SNAPSHOT for now and see if that fixes your issues.
- Kyle
PrimeFaces 6.2 is not compatible with Bridge Impl 4.1.0. We already have made the necessary changes:
- https://github.com/liferay/liferay-faces-bridge-impl/commit/fdd3ac7556a0390f6f5f96d64f430cca7cd14451
- https://github.com/liferay/liferay-faces-bridge-impl/commit/ce36086b94afb4c50f514b83cc9a061ead188704
You can try Bridge Impl 4.1.1-SNAPSHOT for now and see if that fixes your issues.
- Kyle
Kyle Joseph Stiemann:
Hi József,
PrimeFaces 6.2 is not compatible with Bridge Impl 4.1.0. We already have made the necessary changes:
- https://github.com/liferay/liferay-faces-bridge-impl/commit/fdd3ac7556a0390f6f5f96d64f430cca7cd14451
- https://github.com/liferay/liferay-faces-bridge-impl/commit/ce36086b94afb4c50f514b83cc9a061ead188704
You can try Bridge Impl 4.1.1-SNAPSHOT for now and see if that fixes your issues.
- Kyle
Confirmed. 4.1.1-SNAPSHOT solved the issue. Thank you!
Kyle Joseph Stiemann, modified 7 Years ago.
Liferay Master
Posts: 760
Join Date: 1/14/13
Recent Posts
Thanks for trying the SNAPSHOT and confirming that it works, József! Thanks for using Liferay Faces!
Kyle Joseph Stiemann, modified 7 Years ago.
Liferay Master
Posts: 760
Join Date: 1/14/13
Recent Posts
Hi József, we've released Bridge Impl 4.1.1 to maven central (thanks for testing the SNAPSHOT!). You should use that version now.
- Kyle
- Kyle
Hi Kyle Joseph Stiemann,
I use PrimeFaces 6.2 with Liferay Faces Bridge Impl 4.2.5-ga6. And p:fileUpload does not work.
Are there any solutions about this version?My server log after importing file:<Nov 12, 2019 11:22:25 AM GMT+03:00> <Error> <javax.enterprise.resource.webcontainer.jsf.application> <BEA-000000> <Error Rendering View[/views/thyacente/iata-acente-yukleme.xhtml]
java.lang.NullPointerException
at org.primefaces.config.PrimeConfiguration.initConfigFromContextParams(PrimeConfiguration.java:106)
at org.primefaces.config.PrimeConfiguration.<init>(PrimeConfiguration.java:82)
at org.primefaces.context.DefaultApplicationContext.<init>(DefaultApplicationContext.java:41)
at org.primefaces.context.DefaultRequestContext.getApplicationContext(DefaultRequestContext.java:270)
at org.primefaces.metadata.transformer.MetadataTransformerExecutor.processEvent(MetadataTransformerExecutor.java:45)
Truncated. see log file for complete stacktrace
>
Thank you,
Melahat
Hi Melahat,
Liferay Faces Bridge Impl 4.2.5-ga6 is an old supported version. Please use the dropdowns on the home page of liferayfaces.org in order to see which dependencies (and which versions) that you would need to upgrade to. If the problem continues after the upgrade, then please let us know.
Kind Regards,Neil
Liferay Faces Bridge Impl 4.2.5-ga6 is an old supported version. Please use the dropdowns on the home page of liferayfaces.org in order to see which dependencies (and which versions) that you would need to upgrade to. If the problem continues after the upgrade, then please let us know.
Kind Regards,Neil
Hi Neil,If we change our Liferay Faces Bridge Impl version(to 4.1.1), our war doesn' t be Active.And we get this error:weblogic.application.ModuleException: java.lang.ClassNotFoundException: com.liferay.faces.util.product.Product$Name
at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:237)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:232)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
Therefore,
jsf 2.2.8-11,
liferay-faces-bridge-impl 4.2.5-ga6,
liferay-faces-portal 4.2.5-ga6 and liferay-portal-6.2-ce-ga4
Is there any solution with using these versions with primefaces 6.2?Thank you,
Melahat
at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:237)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:232)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
Therefore,
jsf 2.2.8-11,
liferay-faces-bridge-impl 4.2.5-ga6,
liferay-faces-portal 4.2.5-ga6 and liferay-portal-6.2-ce-ga4
Is there any solution with using these versions with primefaces 6.2?Thank you,
Melahat
Hi Melahat,
When you upgrade to the newer (supported) version scheme, you have to upgrade ALL of your Liferay Faces dependencies, including the transitive ones. My best guess is that you didn't upgrade liferay-faces-util.jar (the old transitive dependency) to com.liferay.faces.util.jar (the new transitive dependency). Or, it might be that you are explicitly including dependencies from the old version scheme. I think that the best way for you to know what dependencies to include would be to visit the liferayfaces.org home page and copy the "mvn archetype:generate" command to a local script. Then, run the script in order to generate a project. The generated WAR project will have a pom.xml descriptor with the dependencies you need to explicitly specify. If you don't see <artifactId>com.liferay.faces.util</artifactId> that means it is a transitive dependency and the (Maven) build system will include it automatically in the WEB-INF/lib directory when you build the WAR project.
For more information, refer to the Version Scheme documentation.
Kind Regards,
Neil
When you upgrade to the newer (supported) version scheme, you have to upgrade ALL of your Liferay Faces dependencies, including the transitive ones. My best guess is that you didn't upgrade liferay-faces-util.jar (the old transitive dependency) to com.liferay.faces.util.jar (the new transitive dependency). Or, it might be that you are explicitly including dependencies from the old version scheme. I think that the best way for you to know what dependencies to include would be to visit the liferayfaces.org home page and copy the "mvn archetype:generate" command to a local script. Then, run the script in order to generate a project. The generated WAR project will have a pom.xml descriptor with the dependencies you need to explicitly specify. If you don't see <artifactId>com.liferay.faces.util</artifactId> that means it is a transitive dependency and the (Maven) build system will include it automatically in the WEB-INF/lib directory when you build the WAR project.
For more information, refer to the Version Scheme documentation.
Kind Regards,
Neil
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™