Hello I'd just like to let you know that everything is under control and I didn't abandon the effort.
I've added a todo.txt file[1] to Pax Web's main branch (I didn't create separate GH issues for the tasks yet, as the scope may change, but at some point I'll translate the remaining items to GH issues). So currently (and for some time already) I'm patiently making existing (Pax Web 7) integration tests work with Pax Web 8. The remaining integration tests cover (~10 tests): - HttpContext processing[2] (that's beyond CMPN specifications) - Whiteboard websockets (beyond CMPN specifications) - DTO tests - JAX-RS tests - Jetty/Tomcat/Undertow bundles tests - Jetty Handlers/Connectors OSGi services - VirtualHosts - CRLs - Jasypt The already working (much faster due to better listeners!) tests include (almost 200 per container runtime): - external jetty.xml/tomcat-server.xml/undertow.xml configuration - HttpService/WebContainer tests (CMPN chapter 102) - JSP tests (custom tags, directives, includes, ...) - WABs (including SCIs, WebSockets, scanning and fragments) - JSF - Vaadin (new!) - Whiteboard (much improved, including SCR and standard services) The most important aspects of chapters 102 (Http Service), 128 (Web Applications) and 140 (Whiteboard) are implemented including the most important one - 1:N mapping between web elements and _contexts_. The other most important aspect, not related to CMPN specifications is the consistency of behavior between Jetty, Tomcat and Undertow containers - only ONE integration test has container specific behavior - the test checking HTTP response when POST size (container-specific configuration) is exceeded. I roughly plan to release Pax Web 8 around mid of September. kind regards Grzegorz Grzybek === [1]: https://github.com/ops4j/org.ops4j.pax.web/blob/main/todo.txt [2]: https://ops4j1.jira.com/wiki/spaces/paxweb/pages/354025473/HTTP+Context+processing
