Mihai Mirosanu:
We are using Liferay 6.1 CE GA3 on the jboss 7 bundle.
It sounds like you may have upgraded from 6.1.1, because 6.1.2 CE GA3 was just released last week. Did you upgrade from 6.1.1 CE?
Mihai Mirosanu:
The entire portal is using primefaces portlets.
Cool. How many custom primefaces portlets are you trying to get working?
Mihai Mirosanu:
When we enable portlet cache, the portal does not include tags to require css and js files for jquery and primefaces in the head section.
What do you mean exactly by "portlet cache"? Are these enabled only by portlet deployment descriptor tags like "cache-scope"? or using a liferay specific descriptor such as the "layout-cacheable" tag in your liferay-portlet.xml file? Are these properties you are setting in portal-ext.properties file such as "com.liferay.portal.servlet.filters.cache.CacheFilter"? or some permutation of all the above?
Mihai Mirosanu:
For a not cached page, when viewing the page source we are able to see the js and css tags for primefaces for each portlet on the page.
What version of the
Liferay Faces Bridge are you using? If you are using 6.1.2 CE GA3 you will want to use Liferay Faces Bridge version 3.1.2-ga3 (at this time) in accordance with
this version scheme.
Mihai Mirosanu:
When the same page is cached, the source does not contain anymore those tags, thus giving the console error: Primefaces is not defined or $ is not defined.
Could you try deploying one of the Liferay Faces demos for primefaces such as
the primefaces3-portlet from here to see if that is working in your senario?
And which version of mojarra are you using? Did you
upgrade using these instructions?
Mihai Mirosanu:
Can you please suggest what can we do?
1. Let us know what version of the
Liferay Faces you are using.
2. try one of our primefaces portlets, and let us know if that works.
Mihai Mirosanu:
Is there a known issue regarding this situation?
No known issues for "portlet caching" that I know of.
Hope that helps,
Vernon Singleton
