On 07/07/2020 11:18, Jean-Baptiste Onofre wrote: > Hi everyone, > > It’s more than a year now that we started Apache Karaf 4.3.0 release process, > fully supporting OSGi R7. > > If the 4.3.0 distribution is ready, we are blocked by Pax Web. I’m concerned > about that as R8 will be there and we will have issue in Pax Web again. > > Greg started a huge effort heading to Pax Web 8.0.0 with a large refactoring. > However, the process is long and painful. > So, I think it’s fair to have a discussion about the HTTP service in Karaf > and "relationship" with Pax Web.
Hello, from OpenDaylight perspective, there are four main factors that would drive karaf-4.3.0 adoption: 1) OSGi DS 1.4, for constructor injection This is just nice-to-have to clean up some (small) amount of duplication. 2) Java 14+ support This is for testing, we certainly can do a fair amount of that without Karaf anyway. 3) HTTP Whiteboard 1.1 This is of real interest, as we could ditch our home-grown 'solution' to servlets. 4) JAX-RS Whiteboard 1.0 Just as HTTP, this would allow us to have a clean solution to JAX-RS integration, which we cudgeled to work, but has been a constant source of pain. Based on this, karaf-4.3.0 without R7-compliant HTTP/JAX-RS has very little going for it from our perspective. Also, we do use Equinox as the framework implementation -- perhaps for historical reasons, but it works well and we do not have the cycles to spend on qualifying Felix. Regards, Robert
