jbonofre opened a new pull request, #757:
URL: https://github.com/apache/camel-karaf/pull/757
## Summary
`camel-cxf` unconditionally required `http-whiteboard` (and therefore a
running pax-web/Jetty instance), even though that's only needed for the OSGi
Servlet Whiteboard-based CXF servlet registration added in #687 (the
"Available SOAP Services" listing page). Producer-only usage and consumer
usage via another transport never needed it - `CamelCxfITest` already proves
`camel-cxf` works fine with a manually installed Undertow transport instead,
and `camel-cxf-jetty` provides its own embedded-Jetty transport, so both were
paying for a Jetty-backed OSGi HTTP Service they don't use.
This follows the same pattern already used for `camel-cxf-jetty` and
`camel-cxf-spring`: pull the extra dependency out of the base feature into
its own feature, `camel-cxf-whiteboard` (`camel-cxf` + `http-whiteboard`),
for anyone who wants the whiteboard-registered servlet.
## Changes
- Remove `http-whiteboard` from the base `camel-cxf` feature.
- Add a new `camel-cxf-whiteboard` feature (`camel-cxf` + `http-whiteboard`).
- Add a Pax Exam integration test (`camel-cxf-whiteboard-test`) that installs
the new feature alongside a CXF endpoint served over another transport
(Undertow, same approach as `CamelCxfITest`) and verifies there's no
conflict.
## Test plan
- [x] `CamelCxfWhiteboardITest` (new) passes.
- [x] `CamelCxfITest` and `CamelCxfJettyITest` (existing) still pass
unchanged, confirming the split doesn't break either.
Fixes #755
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
