Hello Let me clarify few things about Pax Web.
Pax Web 8 is almost a complete rewrite of the code and the single reason was ability to register a servlet to multiple "contexts" (requirement from OSGi CMPN Whiteboard specification). Starting from this single issue, I spent almost 3 years rewriting all aspects of Pax Web. Pax Web 9 is THE SAME as Pax Web 8 except two things: - it's JDK11+ - it's using Jetty 10 instead of Jetty 9 (Pax Web 8 will keep JDK8+ requirement). pax-web-extender-war in the version 8.x depends on tomcat so it seems to be > better to switch to pax-web-tomcat-bundle to not bring jetty and tomcat > deps. Unfortunately, it does not work because tomcat stucks in starting > servlet container. You can see it in > https://github.com/apache/aries/pull/453 I'll have a look at https://github.com/apache/aries/pull/453 and check what's the problem there. But mind one thing - pax-web-extender (there are two extenders - whiteboard and war) - does NOT rely on Tomcat _runtime_. It does depend (you can see it in Karaf feature definitions, at Maven level relevant org.apache.tomcat dependencies are with scope=provided) only on scanning/bcel/util/web.xml-parsing bits of Tomcat: pax-web-tomcat-common bundle is Pax Web bundle that exports Tomcat packages responsible for parsing web.xml and fragments and used for code scanning (so ASM is not a requirement) and is used whether you use pax-web-http-tomcat, pax-web-http-jetty or pax-web-http-undertow. I'll try to fix aries/aries#453 this week. regards Grzegorz Grzybek wt., 11 lut 2025 o 21:09 Dominik Przybysz <alien11...@apache.org> napisał(a): > Hi team, > dependabot made a PR to update pax-web in jndi to version 9.x in > https://github.com/apache/aries/pull/356 > It didn't pass the tests because of 8 major versions bump and some other > deps needs to be added. > > Pax web 9.x seems not to support java 8 in runtime so I skipped it in > https://github.com/apache/aries/pull/450 and the highest available version > to update is 8.x > > In https://github.com/apache/aries/pull/452 I was able to bump many of the > JNDI dependencies including pax-web but only to the highest 6.x version. > > Version 7.x of pax-web wasn't able to start and I tried 8.x . > pax-web-extender-war in the version 8.x depends on tomcat so it seems to be > better to switch to pax-web-tomcat-bundle to not bring jetty and tomcat > deps. Unfortunately, it does not work because tomcat stucks in starting > servlet container. You can see it in > https://github.com/apache/aries/pull/453 > > Question: Do you know why in pax-exam tests tomcat is not able to start and > how to fix it? > > -- > Regards, > Dominik Przybysz >
