You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (Resolved JIRA)" <ji...@apache.org> on 2011/11/29 11:01:40 UTC

[jira] [Resolved] (KARAF-942) Expose Karaf RMI registry as a service

     [ https://issues.apache.org/jira/browse/KARAF-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved KARAF-942.
----------------------------------------

    Resolution: Fixed

Revision 1207807.
                
> Expose Karaf RMI registry as a service
> --------------------------------------
>
>                 Key: KARAF-942
>                 URL: https://issues.apache.org/jira/browse/KARAF-942
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-core
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 3.0.0
>
>
> Currently, registering a bean into the Karaf RMI registry is not easy as we are not in the same classloader.
> Especially, it means that the camel-rmi component is not able to work using the Karaf RMI registry (we have to create a registry dedicated in the component classloader).
> If we expose the Karaf RMI registry as an OSGi service (using the java.rmi.registry.Registry interface), we would be able to register the bean without the classloader issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira