I'm pretty sure that Proxy 1.0.0 needs ASM 4.0, 3.3.1 won't work. Regards,
Tim From: [email protected] To: [email protected] Subject: RE: UnableToProxyException with aries 1.0.0 Date: Tue, 25 Sep 2012 02:00:02 +0000 Hi, I’ve checked the ASM but it already has been installed into the container. [ 7] [Active ] [ ] [ ] [ 20] Apache ServiceMix :: Bundles :: asm (3.3.1.1) karaf@admin> exports |grep org.objectweb.asm 7 org.objectweb.asm.util; version="3.3.1" 7 org.objectweb.asm; version="3.3.1" 7 org.objectweb.asm.commons; version="3.3.1" 7 org.objectweb.asm.xml; version="3.3.1" 7 org.objectweb.asm.attrs; version="3.3.1" 7 org.objectweb.asm.signature; version="3.3.1" 7 org.objectweb.asm.tree; version="3.3.1" 7 org.objectweb.asm.tree.analysis; version="3.3.1" (JDK version I’m using is 1.6.0_34) Thanks! Xilai From: Richard Ellis [mailto:[email protected]] Sent: Monday, September 24, 2012 6:30 PM To: [email protected] Subject: Re: UnableToProxyException with aries 1.0.0 I don't think this is the same issue as Aries-908. From the stack it looks to me like it is using the JDK proxy (JdkProxyManager), which suggests to me that ASM is not available. You need ASM for the Aries proxy to be able to do anything more than interfaces and if it was present we should see AsmProxyManager in the stack trace instead. Rich From: Holly Cummins <[email protected]> To: [email protected], Date: 24/09/2012 11:20 Subject: Re: UnableToProxyException with aries 1.0.0 I think you're hitting https://issues.apache.org/jira/browse/ARIES-908. A fix has just been committed for this issue. I wonder if it's an important enough issue that it's worth spinning a proxy 1.0.1 for? Holly --- Enterprise OSGi in Action: http://www.manning.com/cummins On Mon, Sep 24, 2012 at 10:02 AM, XiLai Dai <[email protected]> wrote: > Hello, > > > > I got an UnableToProxyException with Karaf2.3.0/aries 1.0.0 when install a > blueprint based bundle into container. > > > > Caused by: org.apache.aries.proxy.UnableToProxyException: The class > org.talend.esb.sam.agent.feature.EventFeature is not an interface and > therefore a proxy cannot be generated. > > at > org.apache.aries.proxy.impl.JdkProxyManager.getInterfaces(JdkProxyManager.java:43)[12:org.apache.aries.proxy.impl:1.0.0] > > at > org.apache.aries.proxy.impl.JdkProxyManager.createNewProxy(JdkProxyManager.java:36)[12:org.apache.aries.proxy.impl:1.0.0] > > at > org.apache.aries.proxy.impl.AbstractProxyManager.createDelegatingInterceptingProxy(AbstractProxyManager.java:75)[12:org.apache.aries.proxy.impl:1.0.0] > > at > org.apache.aries.proxy.impl.AbstractProxyManager.createDelegatingProxy(AbstractProxyManager.java:40)[12:org.apache.aries.proxy.impl:1.0.0] > > at > org.apache.aries.blueprint.container.AbstractServiceReferenceRecipe.createProxy(AbstractServiceReferenceRecipe.java:299)[9:org.apache.aries.blueprint.core:1.0.0] > > at > org.apache.aries.blueprint.container.ReferenceRecipe.internalCreate(ReferenceRecipe.java:102)[9:org.apache.aries.blueprint.core:1.0.0] > > ... 29 more > > > > The blueprint xml in the bundle: > > <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0";> > > …… > > <reference > xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0"; > ext:proxy-method="classes" id="eventFeature" interface="xxx.xxx.MyClass"/> > > …… > > </blueprint> > > > > ("xxx.xxx.MyClass" is a class, not a interface, so > ext:proxy-method="classes" property added into <reference>) > > > > Any ideas? Thanks! > > > > BR > > Xilai Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
