You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2009/10/15 19:02:31 UTC
[jira] Created: (GERONIMO-4908) RMIClassLoader is not compatible
with osgi
RMIClassLoader is not compatible with osgi
------------------------------------------
Key: GERONIMO-4908
URL: https://issues.apache.org/jira/browse/GERONIMO-4908
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: osgi
Affects Versions: 3.0
Reporter: David Jencks
We have RMIClassLoaderSpiImpl in geronimo-kernel. However, RMIClassLoader loads the spi impl using the system classloader. (http://java.sun.com/javase/6/docs/api/java/rmi/server/RMIClassLoader.html) So we'd have to get our impl into the system classloader unless osgi provides an additional level of delegation in the system classloader.
For now I'm going to try not setting java.rmi.server.RMIClassLoaderSpi in RMIRegistryService
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4908) RMIClassLoader is not compatible
with osgi
Posted by "Rick McGuire (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick McGuire updated GERONIMO-4908:
-----------------------------------
Issue Type: Sub-task (was: Bug)
Parent: GERONIMO-5087
> RMIClassLoader is not compatible with osgi
> ------------------------------------------
>
> Key: GERONIMO-4908
> URL: https://issues.apache.org/jira/browse/GERONIMO-4908
> Project: Geronimo
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: osgi
> Affects Versions: 3.0
> Reporter: David Jencks
> Fix For: 3.0
>
>
> We have RMIClassLoaderSpiImpl in geronimo-kernel. However, RMIClassLoader loads the spi impl using the system classloader. (http://java.sun.com/javase/6/docs/api/java/rmi/server/RMIClassLoader.html) So we'd have to get our impl into the system classloader unless osgi provides an additional level of delegation in the system classloader.
> For now I'm going to try not setting java.rmi.server.RMIClassLoaderSpi in RMIRegistryService
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4908) RMIClassLoader is not compatible
with osgi
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766618#action_12766618 ]
David Jencks commented on GERONIMO-4908:
----------------------------------------
Jarek found that by putting our impl in a jar in lib it is loadable by the standard rm classloader framework. It is not clear to me whether this actually results in bundle classes being accessible through rmi. I guess we should leave this open until we know.
> RMIClassLoader is not compatible with osgi
> ------------------------------------------
>
> Key: GERONIMO-4908
> URL: https://issues.apache.org/jira/browse/GERONIMO-4908
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: osgi
> Affects Versions: 3.0
> Reporter: David Jencks
>
> We have RMIClassLoaderSpiImpl in geronimo-kernel. However, RMIClassLoader loads the spi impl using the system classloader. (http://java.sun.com/javase/6/docs/api/java/rmi/server/RMIClassLoader.html) So we'd have to get our impl into the system classloader unless osgi provides an additional level of delegation in the system classloader.
> For now I'm going to try not setting java.rmi.server.RMIClassLoaderSpi in RMIRegistryService
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4908) RMIClassLoader is not compatible
with osgi
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated GERONIMO-4908:
-----------------------------------
Fix Version/s: 3.0
> RMIClassLoader is not compatible with osgi
> ------------------------------------------
>
> Key: GERONIMO-4908
> URL: https://issues.apache.org/jira/browse/GERONIMO-4908
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: osgi
> Affects Versions: 3.0
> Reporter: David Jencks
> Fix For: 3.0
>
>
> We have RMIClassLoaderSpiImpl in geronimo-kernel. However, RMIClassLoader loads the spi impl using the system classloader. (http://java.sun.com/javase/6/docs/api/java/rmi/server/RMIClassLoader.html) So we'd have to get our impl into the system classloader unless osgi provides an additional level of delegation in the system classloader.
> For now I'm going to try not setting java.rmi.server.RMIClassLoaderSpi in RMIRegistryService
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4908) RMIClassLoader is not compatible
with osgi
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766123#action_12766123 ]
David Jencks commented on GERONIMO-4908:
----------------------------------------
RMI and osgi seems to be a major headache, see for example https://mail.osgi.org/pipermail/osgi-dev/2009-January/001639.html
> RMIClassLoader is not compatible with osgi
> ------------------------------------------
>
> Key: GERONIMO-4908
> URL: https://issues.apache.org/jira/browse/GERONIMO-4908
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: osgi
> Affects Versions: 3.0
> Reporter: David Jencks
>
> We have RMIClassLoaderSpiImpl in geronimo-kernel. However, RMIClassLoader loads the spi impl using the system classloader. (http://java.sun.com/javase/6/docs/api/java/rmi/server/RMIClassLoader.html) So we'd have to get our impl into the system classloader unless osgi provides an additional level of delegation in the system classloader.
> For now I'm going to try not setting java.rmi.server.RMIClassLoaderSpi in RMIRegistryService
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.