Hi Karen Yes, it's pretty similar to what we do in camel-cxf.
Regards JB On Tue, Feb 18, 2025 at 3:50 PM Karen Dolan <kdo...@g.harvard.edu> wrote: > > Hi JB, > > Thank you for this guidance and your work on the Karaf project! > > Does "use private packages” mean creating a custom module like this > https://github.com/apache/camel-karaf/tree/main/components/camel-cxf within > our application to provide access to CXF v4? > > Best Regards, > Karen > > On Jan 31, 2025, at 3:31 AM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > > 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 <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 > > > > >
