Louis, The following is what I installed to get the war-primefaces-wired war to work.
feature:install pax-web-http feature:install pax-web-jsp feature:install pax-web-war feature:install pax-web-karaf feature:install pax-web-websockets feature:install pax-cdi bundle:install mvn:commons-collections/commons-collections/3.2.2 bundle:install mvn:commons-beanutils/commons-beanutils/1.9.4 bundle:install mvn:commons-digester/commons-digester/1.8.1 bundle:install mvn:org.apache.myfaces.core/myfaces-api/2.3.10 bundle:install --start --start-level=84 mvn:org.apache.myfaces.core/myfaces-impl/2.3.10 feature:install jpa bundle:install mvn:jakarta.persistence/jakarta.persistence-api/2.2.3 bundle:install mvn:org.ops4j.pax.web/pax-web-compatibility-jpa2/8.0.27 bundle:install mvn:org.ow2.asm/asm/9.4 bundle:install mvn:org.ow2.asm/asm-tree/9.4 bundle:install mvn:org.ow2.asm/asm-commons/9.4 bundle:install mvn:org.ow2.asm/asm-analysis/9.4 bundle:install mvn:org.ow2.asm/asm-util/9.4 bundle:install --start --start-level=84 mvn:org.apache.aries.spifly/org.apache.aries.spifly.dynamic.bundle/1.3.6 bundle:install --start --start-level=84 mvn:org.primefaces/primefaces/13.0.2 bundle:install --start --start-level=85 mvn:org.ops4j.pax.web.samples/war-primefaces-wired/8.0.27/war Paul Spencer > On Oct 1, 2024, at 3:47 PM, Grzegorz Grzybek <[email protected]> wrote: > > 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] > <mailto:[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.
