[JBoss JIRA] Created: (JBOSGI-205) Document MC/OSGi Service integration
by Thomas Diesler (JIRA)
Document MC/OSGi Service integration
------------------------------------
Key: JBOSGI-205
URL: https://jira.jboss.org/jira/browse/JBOSGI-205
Project: JBoss OSGi
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Assignee: Ales Justin
Please create a section in the user guide that explains what added benefit this MC/OSGi Service integration brings to the user. If applicable, there should be examples that the user can run and look at. This integration work is the first piece of functionality that we do to justify our effort to implement an OSGi core framework, hence special care should be taken to explain and show the actual benefits.
* OSGi services will be exposed as MC beans
I suppose that means you can reference/inject OSGi services in the an MC descriptor. Could you describe/show how this would look like? How would this work with service properties. How would this work with multiple implementations of the same service interface?
* MC beans will be listed as a OSGi services
I suppose that means you can reference/inject MC beans in a BP descriptor. Here as well, could you please describe/show how this would look like? Do MC beans support service properties i.e. Can I use an LDAP filter to find the target service? Can you have multiple implementations of the same service interface? How would the service event model work i.e. Can I use ServiceTracker to track MC beans?
--
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
13 years, 9 months
[JBoss JIRA] Created: (JBOSGI-141) Service integration with MC
by Thomas Diesler (JIRA)
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
13 years, 9 months