[jira] Updated: (TUSCANY-2375) vtest to test generated wsdl
[ https://issues.apache.org/jira/browse/TUSCANY-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2375: -- Attachment: T2375.vtest.zip T2375.vtest.patch > vtest to test generated wsdl > > > Key: TUSCANY-2375 > URL: https://issues.apache.org/jira/browse/TUSCANY-2375 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Assignee: Kevin Williams >Priority: Minor > Attachments: T2375.vtest.patch, T2375.vtest.zip > > > Test the section 2.3.2, 2.3.3, and 2.3.3.1 of WS Binding Spec V1.00 by > examining the generated wsdl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2375) vtest to test generated wsdl
[ https://issues.apache.org/jira/browse/TUSCANY-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2375: -- Attachment: (was: T2375.vtest.patch) > vtest to test generated wsdl > > > Key: TUSCANY-2375 > URL: https://issues.apache.org/jira/browse/TUSCANY-2375 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Assignee: Kevin Williams >Priority: Minor > > Test the section 2.3.2, 2.3.3, and 2.3.3.1 of WS Binding Spec V1.00 by > examining the generated wsdl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2375) vtest to test generated wsdl
[ https://issues.apache.org/jira/browse/TUSCANY-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2375: -- Attachment: (was: T2375.vtest.zip) > vtest to test generated wsdl > > > Key: TUSCANY-2375 > URL: https://issues.apache.org/jira/browse/TUSCANY-2375 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Assignee: Kevin Williams >Priority: Minor > > Test the section 2.3.2, 2.3.3, and 2.3.3.1 of WS Binding Spec V1.00 by > examining the generated wsdl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2375) vtest to test generated wsdl
[ https://issues.apache.org/jira/browse/TUSCANY-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2375: -- Attachment: T2375.vtest.zip T2375.vtest.patch T2375.vtest.patch contains the update and T2375.vtest.zip contains new files > vtest to test generated wsdl > > > Key: TUSCANY-2375 > URL: https://issues.apache.org/jira/browse/TUSCANY-2375 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Assignee: Kevin Williams >Priority: Minor > Attachments: T2375.vtest.patch, T2375.vtest.zip > > > Test the section 2.3.2, 2.3.3, and 2.3.3.1 of WS Binding Spec V1.00 by > examining the generated wsdl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2375) vtest to test generated wsdl
vtest to test generated wsdl Key: TUSCANY-2375 URL: https://issues.apache.org/jira/browse/TUSCANY-2375 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan Priority: Minor Test the section 2.3.2, 2.3.3, and 2.3.3.1 of WS Binding Spec V1.00 by examining the generated wsdl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2367) vtest for binding.ws with promoted services and references
[ https://issues.apache.org/jira/browse/TUSCANY-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2367: -- Attachment: T2367.vtest.patch > vtest for binding.ws with promoted services and references > -- > > Key: TUSCANY-2367 > URL: https://issues.apache.org/jira/browse/TUSCANY-2367 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Priority: Minor > Attachments: T2367.vtest.patch, T2367.vtest.zip > > > Test ws bindings with promoted services and references for section 2.2.2 > 2.3.1, and 2.3.3.1 of WS Binding Spec V1.00 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2367) vtest for binding.ws with promoted services and references
[ https://issues.apache.org/jira/browse/TUSCANY-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2367: -- Attachment: (was: T2367.vtest.patch) > vtest for binding.ws with promoted services and references > -- > > Key: TUSCANY-2367 > URL: https://issues.apache.org/jira/browse/TUSCANY-2367 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Priority: Minor > Attachments: T2367.vtest.zip > > > Test ws bindings with promoted services and references for section 2.2.2 > 2.3.1, and 2.3.3.1 of WS Binding Spec V1.00 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2367) vtest for binding.ws with promoted services and references
[ https://issues.apache.org/jira/browse/TUSCANY-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2367: -- Attachment: T2367.vtest.zip T2367.vtest.patch T2367.vtest.patch contains the update and T2367.vtest.zip contains the new files > vtest for binding.ws with promoted services and references > -- > > Key: TUSCANY-2367 > URL: https://issues.apache.org/jira/browse/TUSCANY-2367 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Priority: Minor > Attachments: T2367.vtest.patch, T2367.vtest.zip > > > Test ws bindings with promoted services and references for section 2.2.2 > 2.3.1, and 2.3.3.1 of WS Binding Spec V1.00 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2367) vtest for binding.ws with promoted services and references
vtest for binding.ws with promoted services and references -- Key: TUSCANY-2367 URL: https://issues.apache.org/jira/browse/TUSCANY-2367 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan Priority: Minor Test ws bindings with promoted services and references for section 2.2.2 2.3.1, and 2.3.3.1 of WS Binding Spec V1.00 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2364) Release vtest atService7 of ServiceAnnotationTestCase
[ https://issues.apache.org/jira/browse/TUSCANY-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2364: -- Attachment: T2364.vtest.patch T2364.vtest.patch is the update > Release vtest atService7 of ServiceAnnotationTestCase > -- > > Key: TUSCANY-2364 > URL: https://issues.apache.org/jira/browse/TUSCANY-2364 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Priority: Minor > Attachments: T2364.vtest.patch > > > http://issues.apache.org/jira/browse/TUSCANY-2191 was fixed and atService7 > should work -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2364) Release vtest atService7 of ServiceAnnotationTestCase
Release vtest atService7 of ServiceAnnotationTestCase -- Key: TUSCANY-2364 URL: https://issues.apache.org/jira/browse/TUSCANY-2364 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan Priority: Minor http://issues.apache.org/jira/browse/TUSCANY-2191 was fixed and atService7 should work -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2363) vtest for soap version and multi soap bindings of binding.ws
[ https://issues.apache.org/jira/browse/TUSCANY-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2363: -- Attachment: T2363.vtest.zip T2363.vtest.patch T2363.vtest.patch is the update and T2363.vtest.zip contains new files > vtest for soap version and multi soap bindings of binding.ws > > > Key: TUSCANY-2363 > URL: https://issues.apache.org/jira/browse/TUSCANY-2363 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Priority: Minor > Attachments: T2363.vtest.patch, T2363.vtest.zip > > > Test soap version and multi soap bindings for section 2.2.2 of WS Binding > Spec V1.00 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2363) vtest for soap version and multi soap bindings of binding.ws
vtest for soap version and multi soap bindings of binding.ws Key: TUSCANY-2363 URL: https://issues.apache.org/jira/browse/TUSCANY-2363 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan Priority: Minor Test soap version and multi soap bindings for section 2.2.2 of WS Binding Spec V1.00 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2348) vTest for ws binding without a WSDL document
[ https://issues.apache.org/jira/browse/TUSCANY-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2348: -- Attachment: T2348.vtest.patch T2348.vtest.zip T2348.vtest.patch is the update and T2348.vtest.zip contains new files > vTest for ws binding without a WSDL document > > > Key: TUSCANY-2348 > URL: https://issues.apache.org/jira/browse/TUSCANY-2348 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Priority: Minor > Attachments: T2348.vtest.patch, T2348.vtest.zip > > > Test section 2.2.2 of SCA WS Binding Specification V1.00 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2348) vTest for ws binding without a WSDL document
vTest for ws binding without a WSDL document Key: TUSCANY-2348 URL: https://issues.apache.org/jira/browse/TUSCANY-2348 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan Priority: Minor Test section 2.2.2 of SCA WS Binding Specification V1.00 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2331) Got expection where the wsdl defines an operation without input
[ https://issues.apache.org/jira/browse/TUSCANY-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598337#action_12598337 ] Gilbert Kwan commented on TUSCANY-2331: --- Surely will do it later. Understand that the limited information at the description may not enough, but just hope someone can look into it in advance if possible. Thanks > Got expection where the wsdl defines an operation without input > --- > > Key: TUSCANY-2331 > URL: https://issues.apache.org/jira/browse/TUSCANY-2331 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan > Attachments: BService.wsdl > > > Got following exception in running where the wsdl defines an operation > without input parameter. > java.lang.IllegalArgumentException: Pass-by-value is not supported for the > given object >at > org.apache.tuscany.sca.databinding.javabeans.JavaBeansDataBinding.copy(JavaBeansDataBinding.java:102) >at > org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint$LazyDataBinding.copy(DefaultDataBindingExtensionPoint.java:171) >at > org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.copy(PassByValueInterceptor.java:235) >at > org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.copyFault(PassByValueInterceptor.java:130) >at > org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:115) >at > org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61) >at > org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108) >at > org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286) >at > org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154) >at $Proxy7.getB1Name(Unknown Source) >at > org.apache.tuscany.sca.vtest.wsbinding.nowsdl.NoWsdlTestCase.testNoWsdl(NoWsdlTestCase.java:62) >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) >at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >at java.lang.reflect.Method.invoke(Method.java:618) >at > org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) >at > org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) >at > org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) >at > org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) >at > org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) >at > org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75) >at > org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36) >at > org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) >at > org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) >at > org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) >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: java.io.NotSerializableException: > org.apache.axiom.om.impl.llom.OMElementImpl >at > java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1113) >at > java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1467) >at > java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1439) >at > java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1382) >at > java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:) >at > java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1467) >at > java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:414) >
[jira] Updated: (TUSCANY-2331) Got expection where the wsdl defines an operation without input
[ https://issues.apache.org/jira/browse/TUSCANY-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2331: -- Attachment: BService.wsdl > Got expection where the wsdl defines an operation without input > --- > > Key: TUSCANY-2331 > URL: https://issues.apache.org/jira/browse/TUSCANY-2331 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan > Attachments: BService.wsdl > > > Got following exception in running where the wsdl defines an operation > without input parameter. > java.lang.IllegalArgumentException: Pass-by-value is not supported for the > given object >at > org.apache.tuscany.sca.databinding.javabeans.JavaBeansDataBinding.copy(JavaBeansDataBinding.java:102) >at > org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint$LazyDataBinding.copy(DefaultDataBindingExtensionPoint.java:171) >at > org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.copy(PassByValueInterceptor.java:235) >at > org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.copyFault(PassByValueInterceptor.java:130) >at > org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:115) >at > org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61) >at > org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108) >at > org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286) >at > org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154) >at $Proxy7.getB1Name(Unknown Source) >at > org.apache.tuscany.sca.vtest.wsbinding.nowsdl.NoWsdlTestCase.testNoWsdl(NoWsdlTestCase.java:62) >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) >at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >at java.lang.reflect.Method.invoke(Method.java:618) >at > org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) >at > org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) >at > org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) >at > org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) >at > org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) >at > org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75) >at > org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36) >at > org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) >at > org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) >at > org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) >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: java.io.NotSerializableException: > org.apache.axiom.om.impl.llom.OMElementImpl >at > java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1113) >at > java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1467) >at > java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1439) >at > java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1382) >at > java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:) >at > java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1467) >at > java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:414) >at java.lang.Throwable.writeObject(Throwable.java:320) >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMetho
[jira] Created: (TUSCANY-2331) Got expection where the wsdl defines an operation without input
Got expection where the wsdl defines an operation without input --- Key: TUSCANY-2331 URL: https://issues.apache.org/jira/browse/TUSCANY-2331 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan Got following exception in running where the wsdl defines an operation without input parameter. java.lang.IllegalArgumentException: Pass-by-value is not supported for the given object at org.apache.tuscany.sca.databinding.javabeans.JavaBeansDataBinding.copy(JavaBeansDataBinding.java:102) at org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint$LazyDataBinding.copy(DefaultDataBindingExtensionPoint.java:171) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.copy(PassByValueInterceptor.java:235) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.copyFault(PassByValueInterceptor.java:130) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:115) at org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154) at $Proxy7.getB1Name(Unknown Source) at org.apache.tuscany.sca.vtest.wsbinding.nowsdl.NoWsdlTestCase.testNoWsdl(NoWsdlTestCase.java:62) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75) at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36) at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) 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: java.io.NotSerializableException: org.apache.axiom.om.impl.llom.OMElementImpl at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1113) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1467) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1439) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1382) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1467) at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:414) at java.lang.Throwable.writeObject(Throwable.java:320) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:972) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1431) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1382) at java.i
[jira] Updated: (TUSCANY-2308) Reference annotation vtest for required=false
[ https://issues.apache.org/jira/browse/TUSCANY-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2308: -- Attachment: T2308.vtest.patch T2308.vtest.patch is the update > Reference annotation vtest for required=false > - > > Key: TUSCANY-2308 > URL: https://issues.apache.org/jira/browse/TUSCANY-2308 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Priority: Minor > Attachments: T2308.vtest.patch > > > @Reference(required=false) and component does not define reference for it -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2308) Reference annotation vtest for required=false
Reference annotation vtest for required=false - Key: TUSCANY-2308 URL: https://issues.apache.org/jira/browse/TUSCANY-2308 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan Priority: Minor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2308) Reference annotation vtest for required=false
[ https://issues.apache.org/jira/browse/TUSCANY-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2308: -- Description: @Reference(required=false) and component does not define reference for it > Reference annotation vtest for required=false > - > > Key: TUSCANY-2308 > URL: https://issues.apache.org/jira/browse/TUSCANY-2308 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Priority: Minor > > @Reference(required=false) and component does not define reference for it -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2289) Java runtime should not inject property into an unannotated non-public field by protected setter
[ https://issues.apache.org/jira/browse/TUSCANY-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593625#action_12593625 ] Gilbert Kwan commented on TUSCANY-2289: --- Should this issue be reassigned to Vamsavardhana Reddy who fixed 2271? > Java runtime should not inject property into an unannotated non-public field > by protected setter > > > Key: TUSCANY-2289 > URL: https://issues.apache.org/jira/browse/TUSCANY-2289 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Assignee: Simon Laws > Fix For: Java-SCA-Next > > > Java Common Annotations and APIs v1.0 - Sec 1.8.13: > 1349 Properties may also be injected via public setter methods even when the > @Property annotation is not > 1350 present. However, the @Property annotation must be used in order to > inject a property onto a non-public > 1351 field. In the case where there is no @Property annotation, the name of > the property is the same as the > 1352 name of the field or setter. > Currently the properties are injected into unannotated protected fields too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2284) Update @Property vtest to test un-annotated non-public field
[ https://issues.apache.org/jira/browse/TUSCANY-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2284: -- Attachment: T2284-vtest.new.zip T2284.vtest.patch T2284.vtest.patch is the updated T2284-vtest.new.zip contains a new file > Update @Property vtest to test un-annotated non-public field > > > Key: TUSCANY-2284 > URL: https://issues.apache.org/jira/browse/TUSCANY-2284 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Assignee: Kevin Williams > Attachments: T2284-vtest.new.zip, T2284.vtest.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2284) Update @Property vtest to test un-annotated non-public field
[ https://issues.apache.org/jira/browse/TUSCANY-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2284: -- Comment: was deleted > Update @Property vtest to test un-annotated non-public field > > > Key: TUSCANY-2284 > URL: https://issues.apache.org/jira/browse/TUSCANY-2284 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Assignee: Kevin Williams > Attachments: T2284-vtest.new.zip, T2284.vtest.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2289) Java runtime should not inject property into an unannotated non-public field by protected setter
[ https://issues.apache.org/jira/browse/TUSCANY-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2289: -- Summary: Java runtime should not inject property into an unannotated non-public field by protected setter (was: Java runtime should inject property into an unannotated non-public field by public setter) > Java runtime should not inject property into an unannotated non-public field > by protected setter > > > Key: TUSCANY-2289 > URL: https://issues.apache.org/jira/browse/TUSCANY-2289 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Assignee: Simon Laws > Fix For: Java-SCA-Next > > > Java Common Annotations and APIs v1.0 - Sec 1.8.13: > 1349 Properties may also be injected via public setter methods even when the > @Property annotation is not > 1350 present. However, the @Property annotation must be used in order to > inject a property onto a non-public > 1351 field. In the case where there is no @Property annotation, the name of > the property is the same as the > 1352 name of the field or setter. > Currently the properties are injected into unannotated protected fields too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2289) Java runtime should inject property into an unannotated non-public field by public setter
[ https://issues.apache.org/jira/browse/TUSCANY-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593616#action_12593616 ] Gilbert Kwan commented on TUSCANY-2289: --- Q 1. protected field and its setter is protected - there should be no injection. A: Only in the case of protected field without a setter method, the property should not be injected. I tested above that un-annotated protected field is injected by its protected setter > Java runtime should inject property into an unannotated non-public field by > public setter > - > > Key: TUSCANY-2289 > URL: https://issues.apache.org/jira/browse/TUSCANY-2289 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Assignee: Simon Laws > Fix For: Java-SCA-Next > > > Java Common Annotations and APIs v1.0 - Sec 1.8.13: > 1349 Properties may also be injected via public setter methods even when the > @Property annotation is not > 1350 present. However, the @Property annotation must be used in order to > inject a property onto a non-public > 1351 field. In the case where there is no @Property annotation, the name of > the property is the same as the > 1352 name of the field or setter. > Currently the properties are injected into unannotated protected fields too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2289) Java runtime should inject property into an unannotated non-public field by public setter
[ https://issues.apache.org/jira/browse/TUSCANY-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2289: -- Comment: was deleted > Java runtime should inject property into an unannotated non-public field by > public setter > - > > Key: TUSCANY-2289 > URL: https://issues.apache.org/jira/browse/TUSCANY-2289 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Assignee: Simon Laws > Fix For: Java-SCA-Next > > > Java Common Annotations and APIs v1.0 - Sec 1.8.13: > 1349 Properties may also be injected via public setter methods even when the > @Property annotation is not > 1350 present. However, the @Property annotation must be used in order to > inject a property onto a non-public > 1351 field. In the case where there is no @Property annotation, the name of > the property is the same as the > 1352 name of the field or setter. > Currently the properties are injected into unannotated protected fields too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2289) Java runtime should inject property into an unannotated non-public field by public setter
[ https://issues.apache.org/jira/browse/TUSCANY-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2289: -- Component/s: (was: Java SCA Verification Tests) Affects Version/s: (was: Java-SCA-1.2) Java-SCA-Next > Java runtime should inject property into an unannotated non-public field by > public setter > - > > Key: TUSCANY-2289 > URL: https://issues.apache.org/jira/browse/TUSCANY-2289 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Assignee: Simon Laws > Fix For: Java-SCA-Next > > > Java Common Annotations and APIs v1.0 - Sec 1.8.13: > 1349 Properties may also be injected via public setter methods even when the > @Property annotation is not > 1350 present. However, the @Property annotation must be used in order to > inject a property onto a non-public > 1351 field. In the case where there is no @Property annotation, the name of > the property is the same as the > 1352 name of the field or setter. > Currently the properties are injected into unannotated protected fields too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2289) Java runtime should inject property into an unannotated non-public field by public setter
[ https://issues.apache.org/jira/browse/TUSCANY-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593614#action_12593614 ] Gilbert Kwan commented on TUSCANY-2289: --- Q 2. protected/private field but its setter is public - there should be no injection, too Ans: No, the property should be injected in this case. I tested the above, where the non-public field is not injected by its public setter. > Java runtime should inject property into an unannotated non-public field by > public setter > - > > Key: TUSCANY-2289 > URL: https://issues.apache.org/jira/browse/TUSCANY-2289 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Assignee: Simon Laws > Fix For: Java-SCA-Next > > > Java Common Annotations and APIs v1.0 - Sec 1.8.13: > 1349 Properties may also be injected via public setter methods even when the > @Property annotation is not > 1350 present. However, the @Property annotation must be used in order to > inject a property onto a non-public > 1351 field. In the case where there is no @Property annotation, the name of > the property is the same as the > 1352 name of the field or setter. > Currently the properties are injected into unannotated protected fields too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2289) Java runtime should inject property into an unannotated non-public field by public setter
Java runtime should inject property into an unannotated non-public field by public setter - Key: TUSCANY-2289 URL: https://issues.apache.org/jira/browse/TUSCANY-2289 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime, Java SCA Verification Tests Affects Versions: Java-SCA-1.2 Reporter: Gilbert Kwan Assignee: Simon Laws Fix For: Java-SCA-Next Java Common Annotations and APIs v1.0 - Sec 1.8.13: 1349 Properties may also be injected via public setter methods even when the @Property annotation is not 1350 present. However, the @Property annotation must be used in order to inject a property onto a non-public 1351 field. In the case where there is no @Property annotation, the name of the property is the same as the 1352 name of the field or setter. Currently the properties are injected into unannotated protected fields too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (TUSCANY-2284) Update @Property vtest to test un-annotated non-public field
[ https://issues.apache.org/jira/browse/TUSCANY-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593454#action_12593454 ] gkwan edited comment on TUSCANY-2284 at 5/1/08 7:21 AM: --- Removed following to rewrite - T2284.vtest.patch contains the update - T2284-vtest.new.zip contains new files This fix will address T2210 and T2271 was (Author: gkwan): T2284.vtest.patch contains the update T2284-vtest.new.zip contains new files This fix will address T2210 and T2271 > Update @Property vtest to test un-annotated non-public field > > > Key: TUSCANY-2284 > URL: https://issues.apache.org/jira/browse/TUSCANY-2284 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Assignee: Kevin Williams > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2284) Update @Property vtest to test un-annotated non-public field
[ https://issues.apache.org/jira/browse/TUSCANY-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2284: -- Attachment: (was: T2284-vtest.new.zip) > Update @Property vtest to test un-annotated non-public field > > > Key: TUSCANY-2284 > URL: https://issues.apache.org/jira/browse/TUSCANY-2284 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2284) Update @Property vtest to test un-annotated non-public field
[ https://issues.apache.org/jira/browse/TUSCANY-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2284: -- Attachment: (was: T2284.vtest.patch) > Update @Property vtest to test un-annotated non-public field > > > Key: TUSCANY-2284 > URL: https://issues.apache.org/jira/browse/TUSCANY-2284 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2284) Update @Property vtest to test un-annotated non-public field
[ https://issues.apache.org/jira/browse/TUSCANY-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2284: -- Attachment: T2284.vtest.patch T2284-vtest.new.zip T2284.vtest.patch contains the update T2284-vtest.new.zip contains new files > Update @Property vtest to test un-annotated non-public field > > > Key: TUSCANY-2284 > URL: https://issues.apache.org/jira/browse/TUSCANY-2284 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan > Attachments: T2284-vtest.new.zip, T2284.vtest.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (TUSCANY-2284) Update @Property vtest to test un-annotated non-public field
[ https://issues.apache.org/jira/browse/TUSCANY-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593454#action_12593454 ] gkwan edited comment on TUSCANY-2284 at 4/30/08 3:40 PM: T2284.vtest.patch contains the update T2284-vtest.new.zip contains new files This fix will address T2210 and T2271 was (Author: gkwan): T2284.vtest.patch contains the update T2284-vtest.new.zip contains new files > Update @Property vtest to test un-annotated non-public field > > > Key: TUSCANY-2284 > URL: https://issues.apache.org/jira/browse/TUSCANY-2284 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan > Attachments: T2284-vtest.new.zip, T2284.vtest.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2284) Update @Property vtest to test un-annotated non-public field
Update @Property vtest to test un-annotated non-public field Key: TUSCANY-2284 URL: https://issues.apache.org/jira/browse/TUSCANY-2284 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (TUSCANY-2271) Java runtime should not inject property into an unannotated non-public field
[ https://issues.apache.org/jira/browse/TUSCANY-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593429#action_12593429 ] gkwan edited comment on TUSCANY-2271 at 4/30/08 1:59 PM: Are followings right? 1. protected field and its setter is protected - there should be no injection. 2. protected/private field but its setter is public - there should be no injection, too was (Author: gkwan): Are followings right? 1. protected field and its setter is protected - there should be no injection. 2. protected/private field but its setter is public - field should be injected. - there should be no injection, too > Java runtime should not inject property into an unannotated non-public field > > > Key: TUSCANY-2271 > URL: https://issues.apache.org/jira/browse/TUSCANY-2271 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime, Java SCA Verification Tests >Affects Versions: Java-SCA-1.2 >Reporter: Vamsavardhana Reddy >Assignee: Vamsavardhana Reddy > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2271.patch > > > Java Common Annotations and APIs v1.0 - Sec 1.8.13: > 1349 Properties may also be injected via public setter methods even when the > @Property annotation is not > 1350 present. However, the @Property annotation must be used in order to > inject a property onto a non-public > 1351 field. In the case where there is no @Property annotation, the name of > the property is the same as the > 1352 name of the field or setter. > Currently the properties are injected into unannotated protected fields too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (TUSCANY-2271) Java runtime should not inject property into an unannotated non-public field
[ https://issues.apache.org/jira/browse/TUSCANY-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593429#action_12593429 ] gkwan edited comment on TUSCANY-2271 at 4/30/08 1:57 PM: Are followings right? 1. protected field and its setter is protected - there should be no injection. 2. protected/private field but its setter is public - field should be injected. - there should be no injection, too was (Author: gkwan): Are followings right? 1. protected field and its setter is protected - there should be no injection. 2. protected/private field but its setter is public - field should be injected. > Java runtime should not inject property into an unannotated non-public field > > > Key: TUSCANY-2271 > URL: https://issues.apache.org/jira/browse/TUSCANY-2271 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime, Java SCA Verification Tests >Affects Versions: Java-SCA-1.2 >Reporter: Vamsavardhana Reddy >Assignee: Vamsavardhana Reddy > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2271.patch > > > Java Common Annotations and APIs v1.0 - Sec 1.8.13: > 1349 Properties may also be injected via public setter methods even when the > @Property annotation is not > 1350 present. However, the @Property annotation must be used in order to > inject a property onto a non-public > 1351 field. In the case where there is no @Property annotation, the name of > the property is the same as the > 1352 name of the field or setter. > Currently the properties are injected into unannotated protected fields too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2271) Java runtime should not inject property into an unannotated non-public field
[ https://issues.apache.org/jira/browse/TUSCANY-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593429#action_12593429 ] Gilbert Kwan commented on TUSCANY-2271: --- Are followings right? 1. protected field and its setter is protected - there should be no injection. 2. protected/private field but its setter is public - field should be injected. > Java runtime should not inject property into an unannotated non-public field > > > Key: TUSCANY-2271 > URL: https://issues.apache.org/jira/browse/TUSCANY-2271 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime, Java SCA Verification Tests >Affects Versions: Java-SCA-1.2 >Reporter: Vamsavardhana Reddy >Assignee: Vamsavardhana Reddy > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2271.patch > > > Java Common Annotations and APIs v1.0 - Sec 1.8.13: > 1349 Properties may also be injected via public setter methods even when the > @Property annotation is not > 1350 present. However, the @Property annotation must be used in order to > inject a property onto a non-public > 1351 field. In the case where there is no @Property annotation, the name of > the property is the same as the > 1352 name of the field or setter. > Currently the properties are injected into unannotated protected fields too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2257) Update and add tests to @Scope vtest
[ https://issues.apache.org/jira/browse/TUSCANY-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2257: -- Attachment: T2257-vtest.new.zip T2257.vtest.patch T2257.vtest.patch contains the update T2257-vtest.new.zip contains new files > Update and add tests to @Scope vtest > > > Key: TUSCANY-2257 > URL: https://issues.apache.org/jira/browse/TUSCANY-2257 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Priority: Minor > Attachments: T2257-vtest.new.zip, T2257.vtest.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2257) Update and add tests to @Scope vtest
Update and add tests to @Scope vtest Key: TUSCANY-2257 URL: https://issues.apache.org/jira/browse/TUSCANY-2257 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan Priority: Minor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2256) Request scope service works as composite scope service
[ https://issues.apache.org/jira/browse/TUSCANY-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2256: -- Description: There are 3 components - JComponent (composite scope) - KComponent (stateless scope) - LComponent (request scope) When the composite runs, composite scope service JComponent kicks off a timer by the @Init method. The timer triggers JComponent every second to invoke a method that calls an operation on the reference to a stateless scope sevice KComponent. KComponent calls a request scope service LComponent multiple times. We found that there was only one instance of LComponent be used and the state was also preserved. Although it was declared as a request scope service, it worked like as a composite scope service. (See the attached powerpoint.) The "SCA Java Annotations And APIs V1" specification line 292 to 293.says, "... the lifetime of the request is implementation dependent.". was: There are 3 components - JComponent (composite scope) - KComponent (stateless scope) - LComponent (request scope) When the composite runs, composite scope service JComponent kicks off a timer by the @Init method. The timer triggers JComponent every second to invoke a method that calls an operation on the reference to a stateless scope sevice KComponent. KComponent calls a request scope service LComponent multiple times. We found that there was only one instance of LComponent be used and the state was also preserved. Although it was declared as a request scope service, it worked like as a composite scope service. (See the attached powerpoint.) The "SCA Java Annotations And APIs V1" specification line 292 to 293.says, "... the lifetime of the request is implementation dependent.". > Request scope service works as composite scope service > -- > > Key: TUSCANY-2256 > URL: https://issues.apache.org/jira/browse/TUSCANY-2256 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan > Attachments: RequestWorkAsComposite.ppt > > > There are 3 components > - JComponent (composite scope) > - KComponent (stateless scope) > - LComponent (request scope) > When the composite runs, composite scope service JComponent kicks off a timer > by the @Init method. The timer triggers JComponent every second to invoke a > method that calls an operation on the reference to a stateless scope sevice > KComponent. KComponent calls a request scope service LComponent multiple > times. > We found that there was only one instance of LComponent be used and the state > was also preserved. Although it was declared as a request scope service, it > worked like as a composite scope service. (See the attached powerpoint.) > The "SCA Java Annotations And APIs V1" specification line 292 to 293.says, > "... the lifetime of the request is implementation dependent.". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2256) Request scope service works as composite scope service
[ https://issues.apache.org/jira/browse/TUSCANY-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2256: -- Attachment: RequestWorkAsComposite.ppt Diagram to show the problem > Request scope service works as composite scope service > -- > > Key: TUSCANY-2256 > URL: https://issues.apache.org/jira/browse/TUSCANY-2256 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan > Attachments: RequestWorkAsComposite.ppt > > > There are 3 components > - JComponent (composite scope) > - KComponent (stateless scope) > - LComponent (request scope) > When the composite runs, composite scope service JComponent kicks off a timer > by the @Init method. The timer triggers JComponent every second to invoke a > method that calls an operation on the reference to a stateless scope sevice > KComponent. KComponent calls a request scope service LComponent multiple > times. > We found that there was only one instance of LComponent be used and the state > was also preserved. Although it was declared as a request > scope service, it worked like as a composite scope service. (See the attached > powerpoint.) > The "SCA Java Annotations And APIs V1" specification line 292 to 293.says, > "... the lifetime of the request is implementation > dependent.". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2256) Request scope service works as composite scope service
Request scope service works as composite scope service -- Key: TUSCANY-2256 URL: https://issues.apache.org/jira/browse/TUSCANY-2256 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan There are 3 components - JComponent (composite scope) - KComponent (stateless scope) - LComponent (request scope) When the composite runs, composite scope service JComponent kicks off a timer by the @Init method. The timer triggers JComponent every second to invoke a method that calls an operation on the reference to a stateless scope sevice KComponent. KComponent calls a request scope service LComponent multiple times. We found that there was only one instance of LComponent be used and the state was also preserved. Although it was declared as a request scope service, it worked like as a composite scope service. (See the attached powerpoint.) The "SCA Java Annotations And APIs V1" specification line 292 to 293.says, "... the lifetime of the request is implementation dependent.". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2234) More tests for section 1.8 of SCA Java Annotations And APIs V100
[ https://issues.apache.org/jira/browse/TUSCANY-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2234: -- Attachment: T2234-vtest.new.zip T2234.vtest.patch > More tests for section 1.8 of SCA Java Annotations And APIs V100 > > > Key: TUSCANY-2234 > URL: https://issues.apache.org/jira/browse/TUSCANY-2234 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Priority: Minor > Attachments: T2234-vtest.new.zip, T2234.vtest.patch > > > Add more tests for following sections > 1.8.1 @AllowsPassByReference > 1.8.3 @ComponentName > 1.8.5 @Constructor > 1.8.6 @Context > 1.8.15 @Remotable -- 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]
[jira] Updated: (TUSCANY-2234) More tests for section 1.8 of SCA Java Annotations And APIs V100
[ https://issues.apache.org/jira/browse/TUSCANY-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2234: -- Description: Add more tests for following sections 1.8.1 @AllowsPassByReference 1.8.3 @ComponentName 1.8.5 @Constructor 1.8.6 @Context 1.8.15 @Remotable was: 1.8.1 @AllowsPassByReference 1.8.3 @ComponentName 1.8.5 @Constructor 1.8.6 @Context 1.8.15 @Remotable > More tests for section 1.8 of SCA Java Annotations And APIs V100 > > > Key: TUSCANY-2234 > URL: https://issues.apache.org/jira/browse/TUSCANY-2234 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Priority: Minor > > Add more tests for following sections > 1.8.1 @AllowsPassByReference > 1.8.3 @ComponentName > 1.8.5 @Constructor > 1.8.6 @Context > 1.8.15 @Remotable -- 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]
[jira] Created: (TUSCANY-2234) More tests for section 1.8 of SCA Java Annotations And APIs V100
More tests for section 1.8 of SCA Java Annotations And APIs V100 Key: TUSCANY-2234 URL: https://issues.apache.org/jira/browse/TUSCANY-2234 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan Priority: Minor 1.8.1 @AllowsPassByReference 1.8.3 @ComponentName 1.8.5 @Constructor 1.8.6 @Context 1.8.15 @Remotable -- 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]
[jira] Created: (TUSCANY-2229) Got WARNING if @Context is used to annotate a setter method
Got WARNING if @Context is used to annotate a setter method
---
Key: TUSCANY-2229
URL: https://issues.apache.org/jira/browse/TUSCANY-2229
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-Next
Reporter: Gilbert Kwan
Priority: Minor
I got following warnings when @Context is used to annotate a setter method:
Apr 15, 2008 11:45:18 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
problem
WARNING: No type specified on component property: BComponent/requestContext
Apr 15, 2008 11:45:18 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
problem
WARNING: No type specified on component property: BComponent/componentContext
Apr 15, 2008 11:45:18 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
problem
WARNING: No type specified on component property: BComponent/requestContext
Apr 15, 2008 11:45:18 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
problem
WARNING: No type specified on component property: BComponent/componentContext
Implementation Class:
=
public RequestContext requestContext;
public ComponentContext componentContext;
@Context
public void setComponentContext(ComponentContext componentContext) {
this.componentContext = componentContext;
}
@Context
public void setRequestContext(RequestContext requestContext) {
this.requestContext = requestContext;
}
Composite:
=
http://www.osoa.org/xmlns/sca/1.0";
targetNamespace="http://java-api-tests";
name="AB-Composite">
If @Context is used to annotate a class field, there is no warning.
--
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]
[jira] Commented: (TUSCANY-2165) Java runtime should inject service references to field with common name in absence of @Reference
[ https://issues.apache.org/jira/browse/TUSCANY-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589165#action_12589165 ] Gilbert Kwan commented on TUSCANY-2165: --- Although b4 is a public field, without setter and un-annotated, should it be injected? - If yes, the patch not work and that why atReference2 failed. - If no, vtest need to rewrite. I tried other scenario b6 which is public field, with setter and un-annotated, it also failed too. I suspect the problem is not fixed yet. I used revision 648306. > Java runtime should inject service references to field with common name in > absence of @Reference > - > > Key: TUSCANY-2165 > URL: https://issues.apache.org/jira/browse/TUSCANY-2165 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Priority: Minor > Attachments: TUSCANY-2165-revised-test.patch, TUSCANY-2165.patch > > > The Java Annotations&APIs specification Lines 1407, 1408, 1409, 1410 ... > * References may also be injected via public setter methods even when the > * "@Reference" annotation is not present. However, the "@Reference" > * annotation must be used in order to inject a reference onto a non > public > * field. In the case where there is no "@Reference" annotation, the name > of > * the reference is the same as the name of the field or setter. > The vTest: > org.apache.tuscany.sca.vtest.javaapi.ReferenceAnnotationTestCase.atReference2 > demonstrates this issue -- 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]
[jira] Commented: (TUSCANY-2199) Tests for @Reference annotation
[ https://issues.apache.org/jira/browse/TUSCANY-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589109#action_12589109 ] Gilbert Kwan commented on TUSCANY-2199: --- I found the patch already applied. > Tests for @Reference annotation > --- > > Key: TUSCANY-2199 > URL: https://issues.apache.org/jira/browse/TUSCANY-2199 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams > Attachments: TUSCANY-2199.multiplicity.test.patch > > > Placeholder for tracking additions to the @Reference vtests -- 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]
[jira] Updated: (TUSCANY-2221) New tests for Java @Scope annotaion
[ https://issues.apache.org/jira/browse/TUSCANY-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2221: -- Attachment: vtest.scope.zip TUSCANY-2221.test.patch > New tests for Java @Scope annotaion > > > Key: TUSCANY-2221 > URL: https://issues.apache.org/jira/browse/TUSCANY-2221 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan >Priority: Minor > Attachments: TUSCANY-2221.test.patch, vtest.scope.zip > > > New tests for Java Common Annotations and APIs Specification of @Scope > annotation -- 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]
[jira] Created: (TUSCANY-2221) New tests for Java @Scope annotaion
New tests for Java @Scope annotaion Key: TUSCANY-2221 URL: https://issues.apache.org/jira/browse/TUSCANY-2221 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan Priority: Minor New tests for Java Common Annotations and APIs Specification of @Scope annotation -- 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]
[jira] Created: (TUSCANY-2215) Destory method is not called if scope type is request
Destory method is not called if scope type is request
-
Key: TUSCANY-2215
URL: https://issues.apache.org/jira/browse/TUSCANY-2215
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-Next
Reporter: Gilbert Kwan
Destroy method was not called for @Scope("REQUEST").
Service Definition:
=
@Scope("REQUEST")
public class AServiceImpl implements AService {
@Init
public void init() {
System.out.println("init()");
}
@Destroy
public void destroy() {
System.out.println("destroy()");
}
public void xxx() {
System.out.println("xxx()");}
}
Client called:
=
System.out.println("Setting up");
domain = SCADomain.newInstance(compositeName);
aService = domain.getService(AService.class, "AService");
aService.xxx();
System.out.println("Cleaning up");
if (domain != null)
domain.close();
Output:
==
Setting up
init()
xxx()
Cleaning up
When changed to other scope type, the destroy method could be called.
--
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]
[jira] Commented: (TUSCANY-2210) Java runtime should inject property to field with common name in absence of @Property
[ https://issues.apache.org/jira/browse/TUSCANY-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586908#action_12586908 ] Gilbert Kwan commented on TUSCANY-2210: --- The vTest to demonstrate this issue will be added by TUSCANY-2211, where the test cases are - org.apache.tuscany.sca.vtest.javaapi.annotations.property.PropertyAnnotationTestCase.atProperty2() - org.apache.tuscany.sca.vtest.javaapi.annotations.property.PropertyAnnotationTestCase.atProperty3() > Java runtime should inject property to field with common name in absence of > @Property > - > > Key: TUSCANY-2210 > URL: https://issues.apache.org/jira/browse/TUSCANY-2210 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Reporter: Gilbert Kwan >Priority: Minor > > The Java Annotations&APIs specification Lines 1349 to 1352: > Properties may also be injected via public setter methods even when the > "@Property" annotation is not present. However, the @Property annotation must > be used in order to inject a property onto a non-public field. In the case > where there is no "@Property" annotation, the name of the property is the > same as the name of the field or setter. > The vTest to demonstrate this issue will be posted later. -- 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]
[jira] Updated: (TUSCANY-2211) New tests for Java @Property annotaion
[ https://issues.apache.org/jira/browse/TUSCANY-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2211: -- Attachment: vtest.property.zip TUSCANY-2211.test.patch > New tests for Java @Property annotaion > --- > > Key: TUSCANY-2211 > URL: https://issues.apache.org/jira/browse/TUSCANY-2211 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Gilbert Kwan > Attachments: TUSCANY-2211.test.patch, vtest.property.zip > > > New tests for Java Common Annotations and APIs Specification of @Property > annotation -- 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]
[jira] Created: (TUSCANY-2211) New tests for Java @Property annotaion
New tests for Java @Property annotaion --- Key: TUSCANY-2211 URL: https://issues.apache.org/jira/browse/TUSCANY-2211 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan New tests for Java Common Annotations and APIs Specification of @Property annotation -- 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]
[jira] Created: (TUSCANY-2210) Java runtime should inject property to field with common name in absence of @Property
Java runtime should inject property to field with common name in absence of @Property - Key: TUSCANY-2210 URL: https://issues.apache.org/jira/browse/TUSCANY-2210 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Reporter: Gilbert Kwan Priority: Minor The Java Annotations&APIs specification Lines 1349 to 1352: Properties may also be injected via public setter methods even when the "@Property" annotation is not present. However, the @Property annotation must be used in order to inject a property onto a non-public field. In the case where there is no "@Property" annotation, the name of the property is the same as the name of the field or setter. The vTest to demonstrate this issue will be posted later. -- 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]
[jira] Updated: (TUSCANY-2199) Tests for @Reference annotation
[ https://issues.apache.org/jira/browse/TUSCANY-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2199: -- Attachment: TUSCANY-2199.multiplicity.test.patch TUSCANY-2199.multiplicity.test.patch contains new tests for multiplicity > Tests for @Reference annotation > --- > > Key: TUSCANY-2199 > URL: https://issues.apache.org/jira/browse/TUSCANY-2199 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams > Attachments: TUSCANY-2199.multiplicity.test.patch > > > Placeholder for tracking additions to the @Reference vtests -- 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]
[jira] Updated: (TUSCANY-2165) Java runtime should inject service references to field with common name in absence of @Reference
[ https://issues.apache.org/jira/browse/TUSCANY-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2165: -- Comment: was deleted > Java runtime should inject service references to field with common name in > absence of @Reference > - > > Key: TUSCANY-2165 > URL: https://issues.apache.org/jira/browse/TUSCANY-2165 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Priority: Minor > Attachments: TUSCANY-2165-revised-test.patch, TUSCANY-2165.patch > > > The Java Annotations&APIs specification Lines 1407, 1408, 1409, 1410 ... > * References may also be injected via public setter methods even when the > * "@Reference" annotation is not present. However, the "@Reference" > * annotation must be used in order to inject a reference onto a non > public > * field. In the case where there is no "@Reference" annotation, the name > of > * the reference is the same as the name of the field or setter. > The vTest: > org.apache.tuscany.sca.vtest.javaapi.ReferenceAnnotationTestCase.atReference2 > demonstrates this issue -- 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]
[jira] Updated: (TUSCANY-2165) Java runtime should inject service references to field with common name in absence of @Reference
[ https://issues.apache.org/jira/browse/TUSCANY-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2165: -- Attachment: (was: TUSCANY-2165.multiplicity.test.patch) > Java runtime should inject service references to field with common name in > absence of @Reference > - > > Key: TUSCANY-2165 > URL: https://issues.apache.org/jira/browse/TUSCANY-2165 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Priority: Minor > Attachments: TUSCANY-2165-revised-test.patch, TUSCANY-2165.patch > > > The Java Annotations&APIs specification Lines 1407, 1408, 1409, 1410 ... > * References may also be injected via public setter methods even when the > * "@Reference" annotation is not present. However, the "@Reference" > * annotation must be used in order to inject a reference onto a non > public > * field. In the case where there is no "@Reference" annotation, the name > of > * the reference is the same as the name of the field or setter. > The vTest: > org.apache.tuscany.sca.vtest.javaapi.ReferenceAnnotationTestCase.atReference2 > demonstrates this issue -- 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]
[jira] Updated: (TUSCANY-2165) Java runtime should inject service references to field with common name in absence of @Reference
[ https://issues.apache.org/jira/browse/TUSCANY-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2165: -- Attachment: TUSCANY-2165.multiplicity.test.patch TUSCANY-2165.multiplicity.test.patch contains new tests for multiplicity > Java runtime should inject service references to field with common name in > absence of @Reference > - > > Key: TUSCANY-2165 > URL: https://issues.apache.org/jira/browse/TUSCANY-2165 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Priority: Minor > Attachments: TUSCANY-2165-revised-test.patch, > TUSCANY-2165.multiplicity.test.patch, TUSCANY-2165.patch > > > The Java Annotations&APIs specification Lines 1407, 1408, 1409, 1410 ... > * References may also be injected via public setter methods even when the > * "@Reference" annotation is not present. However, the "@Reference" > * annotation must be used in order to inject a reference onto a non > public > * field. In the case where there is no "@Reference" annotation, the name > of > * the reference is the same as the name of the field or setter. > The vTest: > org.apache.tuscany.sca.vtest.javaapi.ReferenceAnnotationTestCase.atReference2 > demonstrates this issue -- 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]
[jira] Updated: (TUSCANY-2188) New tests for Java @Service annotaion
[ https://issues.apache.org/jira/browse/TUSCANY-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2188: -- Attachment: FServiceImpl2.zip patches.3.txt patches.3.txt and FServiceImpl2.zip enhances test atService8 * ServiceAnnotationTestCase.java * FServiceImpl.java * service.composite + FServiceImpl2.java p.s. you may ignore patches.2.txt > New tests for Java @Service annotaion > -- > > Key: TUSCANY-2188 > URL: https://issues.apache.org/jira/browse/TUSCANY-2188 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Assignee: Kevin Williams > Attachments: FServiceImpl2.zip, patch.txt, patches.2.txt, > patches.3.txt, service.zip > > > New tests for Java Common Annotations and APIs Specification of @Service > annotation -- 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]
[jira] Issue Comment Edited: (TUSCANY-2188) New tests for Java @Service annotaion
[ https://issues.apache.org/jira/browse/TUSCANY-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585175#action_12585175 ] gkwan edited comment on TUSCANY-2188 at 4/3/08 9:38 AM: --- I updated following by patch.2.txt - ServiceAnnotationTestCase.java about the comments - FServiceImpl.java for test atService8 Still want to know, "What is the different between interfaces and class ? Are both same?" * Line 1637 to 1638: * The service names of the defined services default to the names of the * interfaces or class, without the package name. was (Author: gkwan): I updated - ServiceAnnotationTestCase.java about the comments - FServiceImpl.java for test atService8 Still want to know, "What is the different between interfaces and class ? Are both same?" * Line 1637 to 1638: * The service names of the defined services default to the names of the * interfaces or class, without the package name. > New tests for Java @Service annotaion > -- > > Key: TUSCANY-2188 > URL: https://issues.apache.org/jira/browse/TUSCANY-2188 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Assignee: Kevin Williams > Attachments: patch.txt, patches.2.txt, service.zip > > > New tests for Java Common Annotations and APIs Specification of @Service > annotation -- 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]
[jira] Updated: (TUSCANY-2188) New tests for Java @Service annotaion
[ https://issues.apache.org/jira/browse/TUSCANY-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2188: -- Attachment: patches.2.txt I updated - ServiceAnnotationTestCase.java about the comments - FServiceImpl.java for test atService8 Still want to know, "What is the different between interfaces and class ? Are both same?" * Line 1637 to 1638: * The service names of the defined services default to the names of the * interfaces or class, without the package name. > New tests for Java @Service annotaion > -- > > Key: TUSCANY-2188 > URL: https://issues.apache.org/jira/browse/TUSCANY-2188 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Assignee: Kevin Williams > Attachments: patch.txt, patches.2.txt, service.zip > > > New tests for Java Common Annotations and APIs Specification of @Service > annotation -- 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]
[jira] Updated: (TUSCANY-2188) New tests for Java @Service annotaion
[ https://issues.apache.org/jira/browse/TUSCANY-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Kwan updated TUSCANY-2188: -- Attachment: service.zip patch.txt patch.txt is an update service.zip contains new files. (Please unzip service.zip under vtest\java-api\annotations) > New tests for Java @Service annotaion > -- > > Key: TUSCANY-2188 > URL: https://issues.apache.org/jira/browse/TUSCANY-2188 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Assignee: Kevin Williams > Attachments: patch.txt, service.zip > > > New tests for Java Common Annotations and APIs Specification of @Service > annotation -- 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]
