jamesnetherton commented on issue #5650: URL: https://github.com/apache/camel-quarkus/issues/5650#issuecomment-1893626473
> Any chance you could give more details about why types are leaking? I suspect some class should be ignored somehow but it’s hard to know with the information provided in the issue. I've not really done much a deep dive into it all yet, but, various parts of the Camel core model have JAXB annotations. With `ReflectiveHierarchyBuildItem` now being used, I guess the scope of what's registered for reflection is widened somewhat. For example, I now see classes like `org.apache.camel.spi.Registry`and `org.apache.camel.TypeConverter`being registered for reflection. I don't think that should be necessary, because the Camel registry setup and type converter discovery is done at build time. I also see some third party classes being registered for reflection like `com.azure.storage.queue.QueueServiceClient` & `com.azure.storage.blob.BlobServiceClient`, which I also don't think is necessary. Taking the Azure tests as an example, here's what I see being registered for reflection from the processing of `ReflectiveHierarchyBuildItem`: https://gist.github.com/jamesnetherton/8d00791f61c610a89b30e67a79c4d23b On the flipside, maybe this change has uncovered some potential issues in CQ. E.g the failure in the azure-grouped test is: ``` java.lang.ClassNotFoundException: io.micrometer.core.instrument.Tags ``` Micrometer is an optional dependency of reactor-core (transitive of azure-core), so I'm surprised we've not run into this previously. What worries me a bit is that only a small fraction of the CQ itests have jaxb on the classpath. I wonder what other failures would be uncovered if all of the test modules had it as a dependency.... -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
