JSTL error when deployion thin portlet WAR using primefaces archetype 8.0.1

Development
1

FACES-3744
I found the issue tracked in the public liferay faces jira, is there any news about this ticket?
currenttly using Liferay 7.4 CE GA132

3 Answers

3
2

@neil.griffin I think this one is with you?

3

@Tina_Tian please take a look, thanks.

thanks for your time in reviewing this issue, I think the problem is that jstl is deployed inside the tomcat but javax.faces is inside the osgi container so therefore they can't communicate with each other, is there any workaround i can use?

 –
4

Hi @Mohamed_El_Amin_Zhioua,

https://liferay.atlassian.net/browse/FACES-3744 is no longer reproducible on the latest release of Faces, and this is likely due to the upgrade done to move to the Jakarta namespace. We recommend that you upgrade to 2026.Q1 or later and switch to the Jakarta namespace to use the latest faces release. More information can be found here:

https://learn.liferay.com/w/dxp/development/traditional-java-based-development/developing-a-web-application/using-jsf/upgrading-faces-to-jakarta

Hi Austin, thanks for the reply. The archetype I am using (8.0.1) actually already targets the jakarta namespace. However, upgrading our server runtime to 2026.Q1+ is not possible due to strict project constraints—we must deploy on Liferay CE GA132. Since we cannot change the runtime, we have decided to stick with a thick WAR approach for this project. Bundling our required Jakarta, JSF, and JSTL dependencies directly inside the WAR's WEB-INF/lib seems to be the best workaround to bypass the classloader conflicts. Thanks again!

 –