anonymous wrote : Why do we need Felix?
The reasoning goes like this:
JBossAS wants to leverage core concepts from OSGi, (e.g. jboss services want to provide
classloader semantics to partially expose code that can then be consumed by other jboss
services). This can either be done via jboss proprietary classloading descriptors or via
standard OSGi manifest headers. JBossOSGi is about the latter.
Ultimately, you can deploy standard OSGi bundles as jboss services.
To reach that goal is a parallel effort
#1 Provide an OSGi Framework/Runtime
#2 Migrate jboss services to OSGi bundles
The current idea is that we have an OSGi Facade on top of JBossMC, essentially providing
an OSGi Framework based on MC.
OSGi bundles should not have a dependency on a particular OSGi implementation, instead
they have a dependency on the OSGi core and maybe compendium and other specs.
Having an Apache Felix integration allows us to migrate, test, document, etc our current
services to OSGi while not (yet) having an OSGi Framework implementation that is optimized
for our needs (i.e. JBossMC based)
View the original post :
Reply to the post :