Btw, it seems something has been broken by ARIES-468 a long time ago. Previously, using class proxies was requiring to use the ext namespace handler, because such a behavior was outside the spec. It seems to not be the case anymore, meaning I suppose our implementation is not compliant anymore (unless I missed a spec relax on that point).
I'm mostly referring to https://github.com/apache/aries/commit/24455ce2f04fbdfd207e5953bb6d87b2963eb9d4#diff-5which remove all the references to the ext:proxy-method="class" . Also, since this behavior is outside the spec, I'd like to be able to get back blueprint running without asm + proxy, so that class proxying would be optional and only available when proxy + asm is present (proxy becoming an optional imported package). On Fri, Nov 18, 2011 at 12:08, Guillaume Nodet <[email protected]> wrote: > It seems when I deploy the new proxy manager, all classes are woven which > is very costly in terms of cpu (nearly 45% of Karaf startup time). > Why is that necessary ? Without seing any benefits, I'm not really > prepared to pay that cost. > Any ideas ? > > -- > ------------------------ > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > > -- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
