Hi Nicolas, To do a pull request you can fork the repository then open the pull request from your fork.
The perf boost is interesting but I'd try to not use debouncing which has side effects but just avoid the rewiring which is not needed in the context of a single application. Ultimately services in cxf servlet can be made dynamic at runtime with little effort so can be worth exploring, did you try that before the debouncing? Romain Manni-Bucau @rmannibucau <https://x.com/rmannibucau> | .NET Blog <https://dotnetbirdie.github.io/> | Blog <https://rmannibucau.github.io/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064> Javaccino founder (Java/.NET service - contact via linkedin) Le sam. 4 oct. 2025 à 19:01, Nicolas Brasey <[email protected]> a écrit : > Hi all, > > I just joined the mailing list today and would like to propose an > improvement to the Aries JAX-RS Whiteboard. > > While debugging my application, I was looking for ways to reduce startup > time. I’m working on a relatively large OSGi enterprise application based > on CXF and Karaf. The application uses around 30–40 REST endpoints, which > are registered into CXF by the Aries JAX-RS Whiteboard. > > From what I’ve observed, the current implementation of the JAX-RS > Whiteboard rewires CXF each time a new service is added. This results in a > significant amount of rewiring during application startup, as bundles are > started and services appear. A similar slowdown occurs during shutdown, > when services are being unregistered. > > To address this, I implemented a debouncing mechanism that collects > services and registers them all at once after a configurable period of > stability. With this change, my application’s startup time improved by > roughly 30%. > > If this optimization is of interest to the community, I’d be happy to share > my work and create a pull request. I tried to open one already, but it > seems I don’t have permission to push to the GitHub repository. > > Thanks in advance for your feedback. > > Best regards, > Nicolas Brasey >
