I have investigate the issue a little bit, and looks like the problem is in JavaInterfaceProcessorRegistryImpl. Today, when the service contract is being introspected, it's using the method name as key for the available operations. We need to use a different key approach here, that will take in consideration operation overloading.
BTW, this is probably a common problem in trunk and integration-branch. Thoughts ? Suggestions ? -- Luciano Resende http://people.apache.org/~lresende ---------- Forwarded message ---------- From: Luciano Resende (JIRA) <tuscany-dev@ws.apache.org> Date: Mar 14, 2007 11:12 AM Subject: [jira] Created: (TUSCANY-1173) Can't find method on nested composites with method overloading To: tuscany-dev@ws.apache.org Can't find method on nested composites with method overloading -------------------------------------------------------------- Key: TUSCANY-1173 URL: https://issues.apache.org/jira/browse/TUSCANY-1173 Project: Tuscany Issue Type: Bug Components: Java SCA Kernel Affects Versions: Java-SCA-integration Reporter: Luciano Resende Priority: Critical Fix For: Java-SCA-integration I'm getting this exceptions while running testing/sca/itest/spec. Looks like when we have multiple methods with same name, but with different parameters, they are being lost in JavaInterfaceProcessorRegistryImpl->getOperations as they key is only the method name. ComponentServiceReferenceTestCase->testDefaultService() is one of the test cases that throw this exception. java.lang.reflect.UndeclaredThrowableException at $Proxy24.nextHoliday(Unknown Source) at org.apache.tuscany.sca.test.spec.ComponentServiceReferenceTestCase.testDefaultService (ComponentServiceReferenceTestCase.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.OldTestClassRunner.run( OldTestClassRunner.java:35) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run( JUnit4TestReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run( TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests( RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests( RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run( RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main( RemoteTestRunner.java:196) Caused by: org.apache.tuscany.spi.component.TargetInvocationException: Operation not configured at org.apache.tuscany.core.wire.jdk.JDKInboundInvocationHandler.invoke( JDKInboundInvocationHandler.java:100) ... 21 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
