Hello Putting my opinion on JSF aside, I think I have the answer ;)
Karaf 4.4 is using Pax Web 8 while Karaf 4.2 is using Pax Web 7. This is a huge refactoring of probably every aspect of Pax Web (to make it more specification compliant - whether OSGi CMPN specification or Java Servlet specification). Pax Web 8 includes samples related to JSF (both MyFaces alone and MyFaces + Primefaces and also things like Trinidad/Tobago component libraries) here: https://github.com/ops4j/org.ops4j.pax.web/tree/main/samples/samples-jsf The point is that MyFaces/Primefaces heavily relies on such things as ServletContainerInitializers (to dynamically register filters/servlets/listeners) and WAR path scanning (to look for TLD and faces files). When working on Pax Web 8 I saw that what is now commented ("pax-jsf-support" feature) is actually very tiny, resource-related bridge between JSF and OSGi and as the included samples prove, this "support" wasn't necessary. Please check the samples - if you package your application as WAR/WAB archive there should be no problem installing it and running using Pax Web 8. kind regards Grzegorz Grzybek wt., 1 paź 2024 o 14:43 Luis Lozano <[email protected]> napisał(a): > Good afternoon. > I am currently in the process of migrating my application from karaf > 4.2.16 to karaf 4.4.6 > One of the applications running on my server is implemented using > primefaces (jsf therefore), however I have noticed that the feature > pax-jsf-support is commented out in pax-web-features. > Is there a way to perform this migration? > (I have tried uncommenting pax-jsf-support but I get errors). > Maybe it is time to migrate this application to angular. > > -- > Saludos: > Luis Lozano. >
