Well we can discuss it in another thread but basically commons spirit for me is more basic and shouldn't be a facade (excepted logging). So i'd rather see proxy as an implementation of proxying using asm efficiently. The issue with proxying is not its lifecycle or API in general but its specificities (cache, proxy names, handlers...). The best solution IMO is to propose a unified solution which could be a facade but facade means all impl specificities in its API which makes it harder or specific (in v1 instantiating the factory was a pain IMO since it is specific). ATM the question for me is always which one do i import depending my container, do i test against all proxies impl? Etc... it makes libs hard to write and maintain Le 27 juil. 2013 00:48, "James Carman" <ja...@carmanconsulting.com> a écrit :
> I didn't like the optional dependencies either. Version 2 splits that > stuff out into their own modules with real dependencies, so that fixes > that. > > Has Javassist fixed their memory leaks? If so, we should upgrade our > dependency. > > I guess I don't understand what features you feel are missing. We're > definitely open to feature requests. The proxy types supported were just > what we could come up with at the time. > > On Friday, July 26, 2013, Romain Manni-Bucau wrote: > > > Mem leak through transitive deps (javassist for instance) > > > > Optional is the issue = doesnt work out of the box > > > > I see the project as a facade where id expect features inside (owb proxy > > should be close to reusable). > > > > Btw i dont know v2 so maybe i was irrelevant, i have to check. Thanks for > > pointing it out. > > Le 26 juil. 2013 23:52, "James Carman" <ja...@carmanconsulting.com > <javascript:;>> > > a > > écrit : > > > > > What mem leak? > > > > > > What is wrong with the transitive deps? They're all optional. > > > > > > What proxying logic is missing? > > > > > > On Friday, July 26, 2013, Romain Manni-Bucau wrote: > > > > > > > Mem leak, no transitive dep mgt, few proxying logic so depend a lot > on > > > > others etc... > > > > Le 26 juil. 2013 23:43, "James Carman" <ja...@carmanconsulting.com > <javascript:;> > > > <javascript:;>> > > > > a > > > > écrit : > > > > > > > > > Issues such as? > > > > > > > > > > On Friday, July 26, 2013, Romain Manni-Bucau wrote: > > > > > > > > > > > Commons-proxy you mean? I removed it. ATM we have cdi proxying, > > > > > > aopalliance, ill add a correct aspectj and if we want more well > > > > > use/(update > > > > > > commons proxy to use) asm. Commons proxy brings an easy API > which > > a > > > > > bunch > > > > > > of issues behind ATM IMHO > > > > > > Le 26 juil. 2013 19:26, "James Carman" < > ja...@carmanconsulting.com > > > <javascript:;> > > > > > <javascript:;>> > > > > > > a > > > > > > écrit : > > > > > > > > > > > > > Well, with [proxy], you can get your AOP you're looking for, > too. > > > > > > > > > > > > > > On Wed, Feb 13, 2013 at 3:02 PM, Mark Struberg < > > strub...@yahoo.de> > > > > > > wrote: > > > > > > > > I'm not sure if this is needed in this case. > > > > > > > > > > > > > > > > The Java interceptors spec got moved out of EJB a long time a > > go > > > > and > > > > > is > > > > > > > now a standalone spec which is used by CDI, Spring and guice. > > > > > > > > The package is javax.interceptor and contains all the stuff > we > > > > need. > > > > > > > > > > > > > > > > If we do it in a similar style than Apache MyFaces CODI and > now > > > > > Apache > > > > > > > DeltaSpike does it with the 'InterceptorStrategy' [1] then we > are > > > > > > > completely free of any container specific code. > > > > > > > > > > > > > > > > > > > > > > > > LieGrue, > > > > > > > > strub > > > > > > > > > > > > > > > > [1] > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-deltaspike.git;a=blob;f=deltaspike/core/api/src/main/java/org/apache/deltaspike/core/spi/InterceptorStrategy.java;h=a772152c46ae589572c6bb2bfb0292a8e980b2d3;hb=HEAD > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > >> From: Matt Benson <gudnabr...@gmail.com> > > > > > > > >> To: Commons Developers List <dev@commons.apache.org> > > > > > > > >> Cc: > > > > > > > >> Sent: Wednesday, February 13, 2013 4:39 PM > > > > > > > >> Subject: Re: commons-monitoring? > > > > > > > >> > > > > > > > >> WRT a Commons Interceptor API, [proxy] defines Interceptor > and > > > > other > > > > > > > >> related interfaces. > > > > > > > >> > > > > > > > >> Matt > > > > > > > >> > > > > > > > >> > > > > > > > >> On Wed, Feb 13, 2013 at 6:09 AM, Romain Manni-Bucau > > > > > > > >> <rmannibu...@gmail.com>wrote: > > > > > > > >> > > > > > > > >>> basically having a commons.Interceptor api can be > > interesting > > > > then > > > > > > we > > > > > > > >>> simply need to map to spring and cdi > > > > > > > >>> > > > > > > > >>> this is done in shiro for instance and works very well > > > > > > > >>> > > > > > > > >>> *Romain Manni-Bucau* > > > > > > > >>> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > > > > > > >>> *Blog: >
