Return-Path: Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org Received: (qmail 16122 invoked by uid 500); 7 Aug 2003 15:05:06 -0000 Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list geronimo-dev@incubator.apache.org Received: (qmail 16063 invoked from network); 7 Aug 2003 15:05:06 -0000 Received: from saturn.opentools.org (HELO www.princetongames.org) (66.250.40.202) by daedalus.apache.org with SMTP; 7 Aug 2003 15:05:06 -0000 Received: from localhost (ammulder@localhost) by www.princetongames.org (8.11.6/8.11.6) with ESMTP id h77GZhf02156 for ; Thu, 7 Aug 2003 12:35:43 -0400 X-Authentication-Warning: www.princetongames.org: ammulder owned process doing -bs Date: Thu, 7 Aug 2003 12:35:43 -0400 (EDT) From: Aaron Mulder X-X-Sender: ammulder@www.princetongames.org To: geronimo-dev@incubator.apache.org Subject: Re: Dynamic proxies In-Reply-To: <200308071624.38682.bderidder@novell.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Thu, 7 Aug 2003, Bavo De Ridder wrote: > Don't forget the classloading issues you can have with dynamic proxies. > Interface and implementing class (target) have to be in the same > classloader. This is not true of the Dynamic Proxy features included with the JDK. See the class java.lang.reflect.Proxy, which accepts a ClassLoader to define the proxy in, as well as a list of interfaces for the Proxy to implement. It may well be the case that the ClassLoader you specify must be able to access the interfaces you specify, but I'd have to try to see if that was even enforced. They certainly do not need to all be in the same CL. That said, it may be that App Server X puts additional constraints on their implementation. It would be helpful if you explained exactly what you were trying to do and at what step you run into problems, so we could avoid that for Geronimo. Aaron