For the remote proxies and associated aspects yes, but
I don't want proxy stuff leaking for no good reason. A proxy that can only be
used to cause an exception to be thrown is not a good reason to introduce a new
library dependency on the client. If this was already javassist I would not have
a problem since we likely want an aop container on the client. Leaking asm/cglib
is not something I want to have to do.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clebert Suconic
Sent: Wednesday, February 15, 2006 5:41 PM
To: jboss-development@lists.sourceforge.net; jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] client libraries on EJB3we will need a proxy framework anyways, right?if we replace cglib by something else (aop, javassist maybe) I guess it would be the same on that point, and besides it would require some work.
