[jboss-osgi-issues] [JBoss JIRA] Updated: (JBOSGI-141) Service integration with MC

[Thomas Diesler (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBOSGI-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler updated JBOSGI-141:
----------------------------------

    JBoss Forum Reference: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=160504


> Service integration with MC
> ---------------------------
>
>                 Key: JBOSGI-141
>                 URL: https://jira.jboss.org/jira/browse/JBOSGI-141
>             Project: JBoss OSGi
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Core
>            Reporter: Thomas Diesler
>             Fix For: Framework 1.0.x
>
>
> and vice versa.
> * Service --> MC
> The service layer is not so well integrated with the MC. It does just enough to
> be "OSGi compliant" (of course that's not yet tested). So this is at the
> moment very simple. The OSGiServiceState which should eventually turn into an MC context implementation
> has two "facades", the standard ServiceRegistration and ServiceReference interfaces.
> * MC --> Service
> Services are also largely complete. What's missing is that we want to expose
> MC pojos and JMX MBeans etc. as OSGi services.
> The proper way to do this would be to push the OSGi Filter into kernel project
> and use the MDR INSTANCE scope as the attributes.
> There would be a gotcha in that OSGi expect attributes to have case insensitive names,
> but we would only have to enforce that for OSGi created services.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira