替换Felix SCR注解为OSGi组件注解后服务引用获取及类转换异常求助

将org.apache.felix.scr.annotations替换为org.osgi.service.component.annotations后，无法获取服务引用，启动时抛出类转换异常，同时控制台无法获取bundle、服务或组件信息。

错误日志 #

20:25:41.655 ERROR [AtomixManager] bundle org.onosproject.onos-core-primitives:3.0.0.SNAPSHOT (234)[org.onosproject.store.atomix.impl.AtomixManager(67)] : The activate method has thrown an exception
java.lang.ClassCastException: class io.atomix.cluster.protocol.HeartbeatMembershipProtocol$Type cannot be cast to class io.atomix.utils.NamedType (io.atomix.cluster.protocol.HeartbeatMembershipProtocol$Type is in unnamed module of loader io.github.classgraph.ClassGraphClassLoader @3ade9526; io.atomix.utils.NamedType is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @ea65217)
        at io.atomix.core.registry.ClasspathScanningRegistry.lambda$null$1(ClasspathScanningRegistry.java:80)
        at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
        at io.atomix.core.registry.ClasspathScanningRegistry.lambda$new$2(ClasspathScanningRegistry.java:74)
        at java.base/java.util.Map.computeIfAbsent(Map.java:1003)
        at java.base/java.util.Collections$SynchronizedMap.computeIfAbsent(Collections.java:2682)
        at io.atomix.core.registry.ClasspathScanningRegistry.<init>(ClasspathScanningRegistry.java:68)
        at io.atomix.core.registry.ClasspathScanningRegistry.<init>(ClasspathScanningRegistry.java:43)
        at io.atomix.core.registry.ClasspathScanningRegistry$Builder.build(ClasspathScanningRegistry.java:215)
......
at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:328)
        at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:929)
        at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:915)
        at org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:133)
        at org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:984)
        at org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:752)
        at org.apache.felix.scr.impl.manager.AbstractComponentManager.enableInternal(AbstractComponentManager.java:674)
        at org.apache.felix.scr.impl.manager.AbstractComponentManager$1.run(AbstractComponentManager.java:461)
        at org.apache.felix.scr.impl.ComponentActorThread.run(ComponentActorThread.java:114)

已执行操作 #

在features.xml中添加了以下bundle依赖：

<bundle>mvn:org.osgi/org.osgi.resource/1.0.0</bundle>
<bundle>mvn:org.osgi/org.osgi.service.component/1.4.0</bundle>
<bundle>mvn:org.osgi/org.osgi.service.component.annotations/1.4.0</bundle>
<bundle>mvn:org.osgi/org.osgi.service.metatype.annotations/1.4.0</bundle>

解决建议 #

• 排查类加载冲突：异常显示HeartbeatMembershipProtocol$Type和NamedType来自不同类加载器，说明Atomix相关包可能被多个bundle重复加载，或ClassGraphClassLoader与OSGi类加载器隔离。需确保Atomix所有依赖包由同一类加载器加载，统一在features.xml中引入Atomix依赖，避免版本不一致或重复引入。
• 适配SCR实现版本：替换注解后，需确保Felix SCR版本与OSGi Declarative Services 1.4+兼容，建议升级Felix SCR到2.1.20及以上版本，保证注解处理和组件激活逻辑符合标准。
• 验证注解转换完整性：检查所有原Felix SCR注解是否正确替换为OSGi标准注解，例如@Component的属性（如immediate）是否适配OSGi规范，activate方法签名是否符合要求（如参数类型、修饰符）。
• 补全bundle依赖：确认Atomix相关的所有依赖包都已在features.xml中正确引入，且版本统一，避免因缺失依赖或版本不匹配导致类加载异常。
• 启用类加载调试：添加JVM参数-Dosgi.debug=debug.properties，在debug.properties中配置类加载追踪，查看NamedType和HeartbeatMembershipProtocol$Type的加载来源，准确定位冲突bundle。
• 调整ClassGraph扫描逻辑：Atomix使用ClassGraph扫描类路径，在OSGi环境中需配置ClassGraph使用bundle类加载器，或改用显式注册方式替代ClasspathScanningRegistry，避免跨类加载器的类实例转换问题。

内容的提问来源于stack exchange，提问作者emalovecode