[jboss-dev-forums] [Design of OSGi Integration] - Re: ServiceReferences outside of OSGi Deployers

[adrian@jboss.org]

"johnbailey" wrote : Ok.  I am working on creating a ServiceRegistry.  I am following the advice to use a Deployer to trap all component deployments to get ServiceRegistrations/References for no OSGi deployments.
  | 

That wasn't advice, that was just a hack to get something working until it is done properly. :-)

I don't like the idea of creating an extra registry just to do "indexing" of
component -> deployment
or
feature -> component
(where feature is implemented interface or some property of the service)
we should add this to our native stuff, i.e. the controller/context.

See the discussion I had with Ales about spring-int last year.

SUMMARY: He was adding features only available in the spring integration
(e.g. default create method at the deployment level) when those should have been
available in our native POJOs and spring just reusing them.

anonymous wrote : 
  |  The current ServiceRegistrationImpl is wrapping a KernelControllerContext.  So when the ServiceRegistry receives a component deployment, there isn't a KernelControllerContext available.  Should I lookup the KernelControllerContext from the Kernel, to create the ServiceRegistration?  
  | 

If you're using the hack mentioned above, then you should be able to add
your deployer to the INSTALL stage where you can lookup the ControllerContext
in the Controller using the Component deployment's name.

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

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