Hi Karen, You can take a look on this message: https://lists.apache.org/thread/9gp4v7t6odf8rsmfj6yq1hbfrpglr83p
I proposed to use the same approach as camel-karaf, creating cxf-karaf re-adding/fixing the OSGi/Karaf features. I plan to do that in Q2. As an alternative, you can use the same approach as in camel-karaf, meaning use private packages. Regards JB On Fri, Jan 31, 2025 at 2:04 AM Karen Dolan <[email protected]> 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 > [email protected]
