fipro78 commented on issue #51: URL: https://github.com/apache/felix-atomos/issues/51#issuecomment-1118696424
Well OSGi and JPMS seems to be a bigger issue. :) I tried to create the simple examples using Bndtools and already got quite a lot of problems in that area. Will create a ticket there to share my experiences. For example the require statements where necessary to get the modules compiled in Eclipse and resolved, at runtime it fails with the module path as even the Felix bundles to not provide module infos. Anyhow, if I remove the module-info.class from the corresponding jars, it passes my former modules, but then fails with this: ``` Error occurred during initialization of boot layer java.lang.module.ResolutionException: Modules org.eclipse.osgi.services and org.apache.felix.scr export package org.osgi.service.component to module org.apache.felix.atomos ``` Probably similar to the issue you described above. The Felix setup then works, despite the "modify" command. Probably I forgot to export the package that contains the service implementation. Which is also something I do not fully understand as an OSGi guy. ;) ``` ERROR : bundle org.fipro.modifier.inverter:1.0.0.202205041325 (51)[org.fipro.modifier.inverter.StringInverter(6)] : Error during instantiation of the implementation object java.lang.IllegalAccessException: class org.apache.felix.scr.impl.inject.internal.ComponentConstructorImpl (in module org.apache.felix.scr) cannot access class org.fipro.modifier.inverter.StringInverter (in module org.fipro.modifier.inverter) because module org.fipro.modifier.inverter does not export org.fipro.modifier.inverter to module org.apache.felix.scr ``` At least I know understand the issue better. And I will then continue with the Graal/Substrate example. Thanks a lot for the fast response! -- 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: dev-unsubscr...@felix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
