[~mkouba] {{ClientProxyPrivateMethodsTest}} looks ok from the code standpoint. It may differ from the deployment / environment standpoint as in my use case, the retrieval of the contextual reference is triggered in the {{MetricsExtension}} that is a separate bundle than the bundle that contains the {{MetricRegistry}} class.
To reproduce the issue with the {{MetricsSampleTest}} test, you need to change the scope as you did, and then run the sample into Karaf by running {{mvn test -pl envs/osgi/ -Dtest=MetricsPaxExamTest}}. That executes the same sample into Karaf / OSGi. To debug the test, you need to set [that line|https://github.com/astefanutti/camel-cdi/blob/bc43efb0d51aaf6c3d2c4df41c221c5a8485d811/envs/osgi/src/test/java/org/apache/camel/cdi/osgi/MetricsPaxExamTest.java#L66] to {{true}} and then remote debug.
It may be that these issues are environment related. OSGi, as being more constrained when it comes to class loading, is more sensitive to class proxying issue. Still, I fail to see why the "private nested class" (and the "Package-private class") should not work with OSGi class loading mechanism.
|
