Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Date: Mon, 27 Feb 2012 17:56:48 +0000 (UTC)
From: "Emily Jiang (Updated) (JIRA)" <jira@apache.org>
To: dev@aries.apache.org
Message-ID: 
 <1632976483.23717.1330365408796.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1880599343.23125.1330357848895.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (ARIES-833) Weaving controller switch does not
 work on IBM JVM v6
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ARIES-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emily Jiang updated ARIES-833:
------------------------------

    Attachment: patch-test

I would like to patch the test before this jira is fixed so that I can get the test running on IBM JVM. Can someone cast an eye on it to see whether the test is still valid?

Thanks
Emily
                
> Weaving controller switch does not work on IBM JVM v6
> -----------------------------------------------------
>
>                 Key: ARIES-833
>                 URL: https://issues.apache.org/jira/browse/ARIES-833
>             Project: Aries
>          Issue Type: Bug
>          Components: Proxy
>    Affects Versions: 0.4
>         Environment: IBM JDK6
>            Reporter: Emily Jiang
>         Attachments: patch-test
>
>
> The feature delivered under 'ARIES-826 Add the ability to write a service to control the way proxy weaving works' does not work with IBM JVM v6 when the delegation classes are inner classes(?).
>  The WeavingProxyTest fails on IBM JVM v6. The inner class is an instanceof WovenProxy while it is not on Sun JVM v6, which causes behaviour changes. 
> Runnable r = new Runnable() {
>       public final void run() {
>       }
>     };
> Therefore, checkProxyController test failed on IBM JVM while it passed on Sun JVM.
> Test set: org.apache.aries.proxy.itests.WeavingProxyTest
> -------------------------------------------------------------------------------
> Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.599 sec <<< FAILURE!
> checkProxyController [equinox/3.7.0.v20110613](org.apache.aries.proxy.itests.WeavingProxyTest)  Time elapsed: 3.564 sec  <<< ERROR!
> java.lang.Exception: Unexpected exception, expected<org.apache.aries.proxy.FinalModifierException> but was<java.lang.AssertionError>
>     at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:117)
>     at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:86)
>     at org.ops4j.pax.exam.junit.internal.JUnit4MethodRoadie.runBeforesThenTestThenAfters(JUnit4MethodRoadie.java:60)
>     at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:84)
>     at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:49)
>     at org.ops4j.pax.exam.junit.JUnit4TestRunner.invokeTestMethod(JUnit4TestRunner.java:246)
>     at org.ops4j.pax.exam.junit.JUnit4TestRunner.runMethods(JUnit4TestRunner.java:196)
>     at org.ops4j.pax.exam.junit.JUnit4TestRunner$2.run(JUnit4TestRunner.java:186)
>     at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:34)
>     at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:44)
>     at org.ops4j.pax.exam.junit.JUnit4TestRunner.run(JUnit4TestRunner.java:182)
>     at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
>     at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
>     at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:165)
>     at org.apache.maven.surefire.Surefire.run(Surefire.java:107)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>     at java.lang.reflect.Method.invoke(Method.java:611)
>     at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:289)
>     at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1005)
> Caused by: java.lang.AssertionError: Proxy should not have been woven!
>     at org.junit.Assert.fail(Assert.java:74)
>     at org.apache.aries.proxy.itests.WeavingProxyTest.checkProxyController(WeavingProxyTest.java:116)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>     at java.lang.reflect.Method.invoke(Method.java:611)
>     at org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.injectContextAndInvoke(CallableTestMethodImpl.java:143)
>     at org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.call(CallableTestMethodImpl.java:105)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>     at java.lang.reflect.Method.invoke(Method.java:611)
>     at org.ops4j.pax.exam.rbc.internal.RemoteBundleContextImpl.remoteCall(RemoteBundleContextImpl.java:80)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>     at java.lang.reflect.Method.invoke(Method.java:611)
>     at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)
>     at sun.rmi.transport.Transport$1.run(Transport.java:171)
>     at java.security.AccessController.doPrivileged(AccessController.java:284)
>     at sun.rmi.transport.Transport.serviceCall(Transport.java:167)
>     at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:547)
>     at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:802)
>     at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:661)
>     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
>     at java.lang.Thread.run(Thread.java:736)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira