[jboss-dev-forums] [Design of OSGi Integration] - Re: OSGiControllerContext design

[adrian@jboss.org]

I don't understand your questions without more details or something more
concrete to respond to?

Let me give you my simplistic mapping of the api (the devil is always in the details
which are not included here).

The OSGiControllerContext is an implementation of the OSGi component model
the "service layer" of the OSGi core.

The bundle context is an OSGi personality (as Sacha called it :-) 
of the JBoss Deployer's DeploymentContext.
The "on the fly" part is where we "morph" a JMX or POJO deployment to look like
a OSGi Bundle.
We could also do other deployment types but the others
like ejb or war components map less well as OSGi services.
Certainly, the classloading could be integrated for all deployment types
if they are using an OSGi style classloader.

The bundle activator is like our MainDeployer, but it also has features relating
to the profile service, i.e. programmatic activation of bundles (deployments) from the
repository which is more related to our profile service.

Like I said above, the devil is always in the details, and you are almost certainly
going to have to implement additional features in the JBoss Deployers
so you can hook in the OSGi personality, 
not least the classloading, but also notifications, etc.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025470#4025470

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025470