Implemented an experimental feature in the spirit of the @Proxy concept where
an interface can be given along with an InvocationHandler implementation.
When the bean is created we'd create the InvocationHandler, create a proxy
using the interface, then use the proxy as the bean instance.
Took
Hi great!
I think we already have it through cdi and decorators but it doesnt hurt to
get it this way ;). Fun feature allowing partial impl btw!
Le 21 sept. 2013 12:49, David Blevins david.blev...@gmail.com a écrit :
Implemented an experimental feature in the spirit of the @Proxy concept
where
On Sep 21, 2013, at 4:40 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote:
I think we already have it through cdi and decorators but it doesnt hurt to
get it this way ;).
Similar to decorators, yes. Just as the @Proxy+InvocationHandler concept is
similar to interceptors.
Big difference in
the point is if a method is abstract the bean doesn't know how to impl it
so why should it impl it? an indirection looks mandatory here
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/
Works for me
Le 21 sept. 2013 22:51, David Blevins david.blev...@gmail.com a écrit :
My phrasing might have been off -- I was agreeing with you on all points
:) I was just thinking about how we'd implement it.
We can't instantiate an abstract class so we'd still have to generate a
subclass
Ps: we can reuse a custom handler instead of rewriting a proxy factory with
asm
@PartialBean of deltaspike is more or less the same feature (with scope
handling for handler)
Le 21 sept. 2013 22:56, Romain Manni-Bucau rmannibu...@gmail.com a
écrit :
Works for me
Le 21 sept. 2013 22:51, David
Interesting.
Currently it reuses the @LocalBean code.
-David
On Sep 21, 2013, at 1:59 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote:
Ps: we can reuse a custom handler instead of rewriting a proxy factory with
asm
@PartialBean of deltaspike is more or less the same feature (with
