scottslewis commented on issue #85: URL: https://github.com/apache/felix-atomos/issues/85#issuecomment-2956960044
Is support for dynamic importp something that could be added to atomos...eg with constraints wrt layering? Or is this impossible? I dont think its a killer for rsa, but it does limit generality. Thanks On Mon, Jun 9, 2025, 1:05 PM Thomas Watson ***@***.***> wrote: > *tjwatson* left a comment (apache/felix-atomos#85) > <https://github.com/apache/felix-atomos/issues/85#issuecomment-2956885668> > > e.g. dynamic-importpackage > > I'm not sure if that is a blocker for remote services, but ... > > Dynamic imports are problematic because Atomos gives up the class loader > control to be outside of the framework. For example, there is no actual > class loader for a native compiled app. All the classes are "just there" so > there is no ability to add additional content later that you would > dynamically wire to. Similarly for flat class path there is no way to add > more JARs to the Java class path that would get wired to dynamically. For > Java modules (JPMS), additional module layers can be added dynamically but > the modules (bundles) in the parent layers cannot wire successfully to > modules (bundles) in child layers. And Java modules do not have a concept > of late binding package visibility for the module class loaders. But even > if they did, there is no hook from the Java module class loader that could > notify the OSGi package resolver to do the dynamic import before the class > load can complete/fail. > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/felix-atomos/issues/85#issuecomment-2956885668>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AABHB5AIYV2H47TZJTMSLPL3CXSIRAVCNFSM6AAAAAB65SFBDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNJWHA4DKNRWHA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > -- 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
