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
Liferay 6.2 with Primefaces 4.0
Hello
I have a problem in terms of changing the version of primefaces on ivy.xml, I tried to change:
<dependency name = "org.primefaces.primefaces" org = "com.liferay" rev = "3.5" />
to ward
<dependency name = "org.primefaces.primefaces" org = "com.liferay" rev = "4.0" />
but I have an exeption.
I use Liferay 6.2 with SDK 6.2, please I need your help.
I have a problem in terms of changing the version of primefaces on ivy.xml, I tried to change:
<dependency name = "org.primefaces.primefaces" org = "com.liferay" rev = "3.5" />
to ward
<dependency name = "org.primefaces.primefaces" org = "com.liferay" rev = "4.0" />
but I have an exeption.
I use Liferay 6.2 with SDK 6.2, please I need your help.
Attachments:
Hi amal,
when redeploying a Liferay plugin, you should notice that old jars aren't removed, so if you change any library version, both the old and the new one will coexist and lead to unexpected errors.
Can you try to remove your plugin in /webapps (if using Tomcat) and then deploy your new WAR?
Additionally, take into account that p:confirm is a behavior, not a component, so it should be nested to any ClientBehaviorHolder (like commandButton).
when redeploying a Liferay plugin, you should notice that old jars aren't removed, so if you change any library version, both the old and the new one will coexist and lead to unexpected errors.
Can you try to remove your plugin in /webapps (if using Tomcat) and then deploy your new WAR?
Additionally, take into account that p:confirm is a behavior, not a component, so it should be nested to any ClientBehaviorHolder (like commandButton).
Juan Gonzalez:
Additionally, take into account that p:confirm is a behavior, not a component, so it should be nested to any ClientBehaviorHolder (like commandButton).
Just seen that it needs to nest a org.primefaces.component.api.Confirmable component, so ClientBehavorHolder is not enough (probably you should use p:commandButton).
hello Mr Juan Gonzalez
Thank you for your reply, I tried to romove plugin on my webapps deploy your new WAR.
but I have the same problem outstanding.
for p: confirm I used like this:
<p: commandButton icon = "ui-icon-trash"
action = "# {introBean.delete (introo)}" styleClass = "buttonAction">
<p: confirm header = "Confirmation" message = "Are you sure?" icon = "ui-icon-alert" />
</ p: commandButton>
how will do Mr Juan and thank you for your help.
Thank you for your reply, I tried to romove plugin on my webapps deploy your new WAR.
but I have the same problem outstanding.
for p: confirm I used like this:
<p: commandButton icon = "ui-icon-trash"
action = "# {introBean.delete (introo)}" styleClass = "buttonAction">
<p: confirm header = "Confirmation" message = "Are you sure?" icon = "ui-icon-alert" />
</ p: commandButton>
how will do Mr Juan and thank you for your help.
Can you post here the list of jar libraries located in your deployed WAR inside webapps/<YOUR_PORTLET>/WEB-INF/lib directory?
Hello Mr Juan
thanks for your answer ,here are the JAR:
I delete primefaces.jar and org.primefaces.primefaces.jar and redeplyer tomcat to show my portles if not it does not display.
during deployement of my portlet 2 primefaces.jar jar and automatically add org.primefaces.primefaces.jar !!
thanks for your answer ,here are the JAR:
I delete primefaces.jar and org.primefaces.primefaces.jar and redeplyer tomcat to show my portles if not it does not display.
during deployement of my portlet 2 primefaces.jar jar and automatically add org.primefaces.primefaces.jar !!
Attachments:
amal miftahi:
Hello Mr Juan
thanks for your answer ,here are the JAR:
I delete primefaces.jar and org.primefaces.primefaces.jar and redeplyer tomcat to show my portles if not it does not display.
during deployement of my portlet 2 primefaces.jar jar and automatically add org.primefaces.primefaces.jar !!
So, as I suspected you have duplicated liferay-faces and primefaces libraries (the latter you have 3 of them!).
So you have to remove your currently deployed portlet, then do "ant clean deploy".
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™