XPCOMJavaProxyBase belongs in impl jar, not interfaces jar. No bug. Not part of default build

Original committer: pedemont%us.ibm.com
Original revision: 1.3
Original date: 2005/11/22 23:09:08
This commit is contained in:
pedemont%us.ibm.com 2006-09-27 15:13:25 +00:00
Родитель c640f3ef93
Коммит 0464047fab
1 изменённых файлов: 7 добавлений и 1 удалений

Просмотреть файл

@ -83,7 +83,13 @@ public class XPCOMJavaProxy implements InvocationHandler {
* @return Proxy of given XPCOM object
*/
protected static Object createProxy(Class aInterface, long aXPCOMInstance) {
return Proxy.newProxyInstance(aInterface.getClassLoader(),
// XXX We should really get the class loader from |aInterface|. However,
// that class loader doesn't know about |XPCOMJavaProxyBase|. So for
// now, we get the class loader that loaded |XPCOMJavaProxy|. When
// we get rid of the "XPCOMJavaProxyBase.java" class, we can revert
// to the old method below.
// return Proxy.newProxyInstance(aInterface.getClassLoader(),
return Proxy.newProxyInstance(XPCOMJavaProxy.class.getClassLoader(),
new Class[] { aInterface, XPCOMJavaProxyBase.class },
new XPCOMJavaProxy(aXPCOMInstance));
}