commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Carman <>
Subject Re: [proxy] and impl
Date Sat, 27 Jul 2013 14:05:17 GMT
While I get what you're saying, that's kind of the entire reason
Commons Proxy was created.  Proxy came about from my experience with
Apache HiveMind and Javassist.  We were constantly doing Javassist
coding each time we wanted new proxying logic.  There was a LOT of
repeated code because of all the commonality.  After a couple years of
doing this, I decided to create a library which would consolidate that
logic into one library and allow the user to provide small "snippets"
(Interceptors, Invokers, ObjectProvider) to achieve what they wanted
to do.

You're right, Commons Proxy doesn't really fit in Apache Commons
perfectly, since it is very "frameworky", but we decided to roll it in

Anyway, so much for a history lesson. :)  I have wanted an ASM-based
proxy factory for a long time, but have just never had the time to get
around to it.  If you want to help us create an ASM-based proxy
factory implementation, that would be great!  I'm no ASM expert, so I
wouldn't even know where to start.

On Sat, Jul 27, 2013 at 9:51 AM, Romain Manni-Bucau
<> wrote:
> Hi
> On a mail on [monitoring] i put some point on proxy. The main question was
> shouldnt proxy give a default impl of proxying instead of being a facade
> (which needs to put all impl specifities in the api or a way to get them)?
> In tomee/openejb and owb we use asm to create proxies and InvocationHandler
> standard interface. That's very powerful and insanely fast.
> Asm also provides some helpers like
> My question is then: shouldnt proxy2 change a bit of spirit?

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message