[jboss-dev-forums] [Design of OSGi Integration] - Re: Facade Questions

[adrian@jboss.org]

"johnbailey" wrote : Ok.  I will start on the facade assuming there will be at least a DeploymentUnit available.  If the Unit has an attached ControllerContext, it will delegate to the attached version, otherwise it will create a DeployentContollerContext.  Does this seem like the correct approach?
  | 

They will always be available. The only time you need to create them
in the OSGi layer is in the BundleContext::installBundle() methods
which you will do indirectly by delegating to the main deployer.

anonymous wrote : 
  | It seems like the BundleContext will need access to the DeploymentUnit in order to create ServiceReferences, which I see as components of the Deployment.  Make sense?
  | 

Yes, ServiceReferences are deployment components that
are installed as "ServiceReferenceControllerContexts" into the MC. 

They're really just facades on top of any ControllerContext.

This allows us to expose MBeans and POJOs (using the same facade)
as OSGi services and also potentially dependency inject OSGi
services into mbeans and pojos.

Ales can tell you which parts are already done and what the classes
are really called, the devil is always in the details. ;-)

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

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