ppalaga commented on issue #8245: URL: https://github.com/apache/camel-quarkus/issues/8245#issuecomment-3859372229
> how best to solve this? First, why this happens: 1. Quarkus JAXB registers classes with JAXB annotations using ReflectiveHierarchyStep 2. The set of classes selected by ReflectiveHierarchyStep is sometimes unintuitive 3. Some Camel Core classes have JAXB annotations, probably to support defining routes in XML (or is it only for historical reasons to dump the model to XML?) 4. Some of the classes ReflectiveHierarchyStep pulls in are not in Jandex 5. Some of the classes ReflectiveHierarchyStep pulls in are not in class path (because they are optional deps or excluded by us deliberately (such as Spring)). Now how these points can be addressed: * 1 seems to be correct * 2 perhaps fixable in some cases. E.g. we could propose a new `ignoreNonLoadableClasses` flag on ReflectiveHierarchyStep that would prevent issues 4. and 5. * 3 we might want to review whether those Camel classes really require JAXB annotations * 4 Are netty jars indexed? If not, using IndexDependencyBuildItem might be a quick workaround. * 5 The attached log does not look like we have this kind of problem. Just for the sake of completeness: in QCXF, I have implemented some bytecode transformation to get rid of Spring refs in CXF. -- 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]
