Hi,
Actually, you will have three class loader levels:
- Level1: Karaf itself/Karaf services/libraries class loaders
- Level2: profiles class loader
- Level3: OSGi module running in the internal framework (inheriting first level)
- Level3: Spring Boot applications classloaders
- Level3: other kind of applications (micro profile, …)
So, basically, framework will be used for OSGi modules mostly.
Today, launchers are "isolated", but I will implement bridges.
Regards
JB
> Le 24 mars 2021 à 15:37, Grzegorz Grzybek <gr.grzy...@gmail.com> a écrit :
>
> Hello
>
> OSGi Core R8 still assumes req/cap model[1] and resolution:
>
> The Framework must resolve bundles.
>>
>
> If OSGi (and thus resolution) is _internal_, what kind of "classpath"
> ("module path"?) will users see? Looking forward for 10000-feet overview of
> Karaf 5 ;)
>
> Is Connect specification[2] the inherent part of Karaf5? Is "classpath"
> generally flat, hierarchical or irrelevant (?) by default?
>
> Anyway - the future looks bright ;)
>
> regards
> Grzegorz Grzybek
> ===
> [1]:
> https://docs.osgi.org/specification/osgi.core/8.0.0/framework.module.html#framework.module-resolving
> [2]:
> https://docs.osgi.org/specification/osgi.core/8.0.0/framework.connect.html
>
> śr., 24 mar 2021 o 15:24 Jean-Baptiste Onofre <j...@nanthrax.net> napisał(a):
>
>> Hi guys,
>>
>> As you probably know, we are working on first Karaf 5 MVP, which is a
>> complete Karaf refactoring.
>>
>> We will share some details soon, but I can already inform you that
>> internally, it’s powered by OSGi R8 (but you will see that it’s more an
>> internal point).
>>
>> Regards
>> JB
