[jboss-dev-forums] [Design of OSGi Integration] - Re: Why do we need a Felix integration

[adrian@jboss.org]

anonymous wrote : 
  | Hi Scott/Adrian,
  | 
  | perhaps you could comment on
  | 
  | http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222021#4222021
  | 
  | I'd like to understand better what an MC based OSGi Framework 
  | implementation may offer over any other OSGi Framwork implementation.
  | 

My thoughts can be found in the earlier posts in this forum, e.g.
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=103025
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=130500
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=131151
Those + other threads explain how I see it being implemented.

Basically all JBoss deployments and services should appear to the OSGi api user
as OSGi bundles/services. (Eventually, that includes for example being able to get a
service reference on an EJB remote/local interface.)
To me this is the key feature since OSGi provides a standard api for controlling
deployments and services instead of using a non-spec jboss api.

And vice-versa you should be able to inject OSGi services into pojos/mbeans, etc.

This should be as seamless as possible.
OSGi bundle <-> Deployment
ServiceReference <-> MC ControllerContext

Somebody deploying a POJO shouldn't have to implement an OSGi api
to make it work, that defeats the point of them being POJOs,

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

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