Hi Matt, I think it's partially related to Pax Web, but not only (it's possible to use Felix Http as a temp workaround or private package in bundle). The main "blocker" is about OSGi Header/Karaf Features in CXF 4.x.
Regards JB On Fri, Jan 31, 2025 at 3:54 AM Matt Pavlovich <mattr...@gmail.com> wrote: > > Hi Karen- > > Karaf support for Jakarta-based servlets requires an update to the Pax Web > project to support Jetty 12 and Jakarta-based servlets. There is a lot of > interest and desire to get this going amongst the user base. > > The lead committer on Pax Web has made a good start on it, but it requires > more work to complete. > > I’ve started on Jetty 12 support for ActiveMQ, and once that is done I hope > to have some time to put into Pax Web as well. > > Thanks, > Matt Pavlovich > > On Jan 30, 2025, at 7:04 PM, Karen Dolan <kdo...@g.harvard.edu> wrote: > > Hi All, > > We really want to migrate from javax.servlet to jakarta.servlet but we use > the cxf provided in Karaf. The latest version is still cxf 3.x. That cxf > still requires javax.servlet. > > There is an open Jira ticket from Sept 2023 saying that Karaf 4.5.x will have > full Jakarta, which maybe implies cxf 4x support. > https://issues.apache.org/jira/browse/KARAF-7749 > > Does anyone know if Karaf is planning to support cxf 4 in the near (months vs > years) future? Or have an alternative recommendation? For example, could > Karaf-camel be used in a low impact way without requiring us to rewrite our > module’s endpoint config ? > > Thank you, > Karen > > -------------------------------- > Karen Dolan > Software Engineering Team for Teaching and Learning > Harvard University > Division of Continuing Education > 125 Mount Auburn Street > Cambridge, MA 02138 > karen_do...@harvard.edu > >
