Thanks for the clarification
Christian
Am 21.06.2012 09:51, schrieb Richard Ellis:
Hi Christian,
Weaving is enabled by default for an OSGi 4.3 environment with ASM.
However, there were some concerns raised about weaving every class so two
methods of control were introduced:
1. Providing an implementation of the
org.apache.aries.proxy.weavinghook.ProxyWeavingController interface (see
https://issues.apache.org/jira/browse/ARIES-826)
2. Using the system properties org.apache.aries.weaving.enabled or
org.apache.aries.proxy.weaving.disabled (see
https://issues.apache.org/jira/browse/ARIES-786)
I don't know if any Karaf config or bundles use these methods to limit or
disable weaving entirely, but if the class for which the proxy was
requested has not been woven then the proxy code will fall back to
generating a subclass proxy.
Hope that helps,
Rich
From: Christian Schneider<ch...@die-schneider.net>
To: dev@aries.apache.org,
Date: 15/06/2012 21:18
Subject: Re: Latest JDK and ASM based proxies....
Sent by: Christian Schneider<cschneider...@googlemail.com>
We are experiencing the problems in Karaf 3 SNAPSHOT.
This is based on OSGi 4.3 and aries 1.0.0-SNAPSHOT. Still it does not
work. Is there anything
special to enable the WavingHook support?
Christian
Am 15.06.2012 15:47, schrieb Richard Ellis:
I believe that this problem is limited to the subclass proxy and not the
newer improved WeavingHook based proxy. So for cases where people want
to
use both a very recent JVM and a class that does not have an accessible
zero-arg constructor there is the option to move up to use proxy 0.4 and
an OSGi 4.3 based framework.
Rich
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
