[ mx4j-Bugs-907629 ] Class loading problem at RMIConnectorServer.start()
"SourceForge.net" <[email protected]>
| Newsgroups | gmane.comp.java.mx4j.devel |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #907629, was opened at 2004-03-01 07:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=450647&aid=907629&group_id=47745 Category: JSR 160 Implementation Group: Release 2.0.0 Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Class loading problem at RMIConnectorServer.start() Initial Comment: The problem is that at mx4j.remote.ConnectionResolver.getInstance(String proto) the class loader used is the thread's context class loader, even if in the enviroment map, another classloader is passed. Thus, if you are using mx4j inside a platform such as OSGi, an java.net.MalformedURLException: Unsupported protocol: rmi will be raised ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=450647&aid=907629&group_id=47745 ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click