"scott.stark(a)jboss.org" wrote : Its not clear that this is the right thing to do
as mapping osgi onto spring on top of the mc is not what we want. What we want is a
mapping of the osgi concepts onto the mc metdata/wiring of the beans with help from
supporting osgi interface implementations.
I wouldn't go over Spring to map it to MC.
I ment that we can go in the same impl direction - core + starter (extender) bundle. But
definitely with our metadata/wiring.
"scott.stark(a)jboss.org" wrote :
| The starting point should be usecases decribing what we mean by support for osgi.
I would support similar things as the Spring spec (+ joined work of OSGi EG members)
supports - as I went over that, I saw no problems that we might have with implementing
this on top of MC.
That is a simple introduction of additional OSGi based XML (annotation) definition - OSGi
service, reference, ... - but wired with existing MC beans.
View the original post :
Reply to the post :