reta commented on a change in pull request #904:
URL: https://github.com/apache/cxf/pull/904#discussion_r819175354
##
File path:
rt/frontend/simple/src/main/java/org/apache/cxf/frontend/WSDLGetUtils.java
##
@@ -566,9 +566,6 @@ private void processSchemaReference(SchemaReferenc
Hey guys,
Also +1 to @Jim's suggestion, it would also unblock us on supporting latest
JDKs
promptly. Going with something like cxf-karaf integration in separate repository
+ release cycle makes sense to me. @Jim, I know you have started to look at
Spring specifically, but tackling Karaf/OSGi wo
Hi,
Think it makes sense to split a bit CXF in a strong "core" leveraging
minimal dependency (thinking strongly to servlet there which enables most
of the runtimes from standalone to EE without forgetting microprofile and
OSGi) and extract outside the core project all integrations which have
diffe
Hi Jim,
+1 to comment out OSGi bit for now so this won't block the whole Jakarta
namespace migration work on CXF 4.x. And we can move fast without waiting
for the OSGi spec to be JakartaEE9+ compatible.
Going forward, I think we can extract the CXF OSGi/Karaf to a subproject of
CXF, maybe with
