[jira] Created: (TUSCANY-2390) Default property value in Component Type Fiel not used to initialize property
Default property value in Component Type Fiel not used to initialize property - Key: TUSCANY-2390 URL: https://issues.apache.org/jira/browse/TUSCANY-2390 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams I modified a working test to initialize a property from the component type file rather than the .composite and the test now fails. org.apache.tuscany.sca.vtest.assembly.ctypefile.CompomnentTypeFileTestCase.typeFile3() demonstrates this problem and has been @Ignore(d) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2375) vtest to test generated wsdl
[ https://issues.apache.org/jira/browse/TUSCANY-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2375. --- Resolution: Fixed > 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-2383) Cannot define component property with Component Type File
Cannot define component property with Component Type File - Key: TUSCANY-2383 URL: https://issues.apache.org/jira/browse/TUSCANY-2383 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Lines 450-451 of the Assembly spec: The componentType element can contain Service elements, Reference elements and Property elements. I defined a test that inspects an injected property value. In the initial version I defined the property using the @Property annotation. I then tried replacing the annotation with an entry in a Component Type File without success. The test: org.apache.tuscany.sca.vtest.assembly.ctypefile.CompomnentTypeFileTestCase.typeFile3 demonstrates this failure and is currently @Ignore(d) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2375) vtest to test generated wsdl
[ https://issues.apache.org/jira/browse/TUSCANY-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams reassigned TUSCANY-2375: --- Assignee: Kevin Williams > 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] Closed: (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 ] Kevin Williams closed TUSCANY-2367. --- Resolution: Fixed > 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 >Assignee: Kevin Williams >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] Assigned: (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 ] Kevin Williams reassigned TUSCANY-2367: --- Assignee: Kevin Williams > 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 >Assignee: Kevin Williams >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] Closed: (TUSCANY-2364) Release vtest atService7 of ServiceAnnotationTestCase
[ https://issues.apache.org/jira/browse/TUSCANY-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2364. --- Resolution: Fixed > 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 >Assignee: Kevin Williams >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] Closed: (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 ] Kevin Williams closed TUSCANY-2363. --- Resolution: Fixed > 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 >Assignee: Kevin Williams >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] Assigned: (TUSCANY-2364) Release vtest atService7 of ServiceAnnotationTestCase
[ https://issues.apache.org/jira/browse/TUSCANY-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams reassigned TUSCANY-2364: --- Assignee: Kevin Williams > 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 >Assignee: Kevin Williams >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] Assigned: (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 ] Kevin Williams reassigned TUSCANY-2363: --- Assignee: Kevin Williams > 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 >Assignee: Kevin Williams >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] Closed: (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 ] Kevin Williams closed TUSCANY-2348. --- Resolution: Fixed > 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 >Assignee: Kevin Williams >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] Assigned: (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 ] Kevin Williams reassigned TUSCANY-2348: --- Assignee: Kevin Williams > 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 >Assignee: Kevin Williams >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] Commented: (TUSCANY-2247) vtest content for Java API spec - Conversation/Async
[ https://issues.apache.org/jira/browse/TUSCANY-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597491#action_12597491 ] Kevin Williams commented on TUSCANY-2247: - Leaving this open until resolution of TUSCANY-2312 at which point I will add testing for section 1.6.7.5 which will complete conversation testing. > vtest content for Java API spec - Conversation/Async > - > > Key: TUSCANY-2247 > URL: https://issues.apache.org/jira/browse/TUSCANY-2247 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Assignee: Kevin Williams > Fix For: Java-SCA-Next > > > Add vtest content for Java API/Annotation Spec section 1.6 - Conversations > and Async -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2312) Runtime ignores custom callback when using setCallback()
Runtime ignores custom callback when using setCallback() Key: TUSCANY-2312 URL: https://issues.apache.org/jira/browse/TUSCANY-2312 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams The Java CAA spec states: /** * Lines 728-732 * * By default, the client component of a service is assumed to be the * callback service for the bidirectional service. However, it is possible * to change the callback by using the ServiceReference.setCallback() * method. The object passed as the callback should implement the interface * defined for the callback, including any additional SCA semantics on that * interface such as its scope and whether or not it is remotable. */ I am getting the following error when I try to provide a custom callback using ServiceReference.setCallback(). I appears that the runtime has injected the client service as the callback rather then the user provided callback resulting in the following exception: java.lang.IllegalArgumentException: java.lang.NoSuchMethodException: No matching method for operation callBack is found on class org.apache.tuscany.sca.vtest.javaapi.conversation.callback.custom.impl.AServiceImpl at org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationProvider.createInvoker(JavaImplementationProvider.java:148) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addImplementationInterceptor(RuntimeWireImpl.java:315) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:188) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:109) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChain(RuntimeWireImpl.java:115) at org.apache.tuscany.sca.core.assembly.RuntimeComponentServiceImpl.getInvocationChain(RuntimeComponentServiceImpl.java:120) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.getInvoker(RuntimeSCAReferenceBindingProvider.java:184) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.createInvoker(RuntimeSCAReferenceBindingProvider.java:197) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addReferenceBindingInterceptor(RuntimeWireImpl.java:228) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:167) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:109) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.getInvocationChain(JDKInvocationHandler.java:243) at org.apache.tuscany.sca.core.invocation.JDKCallbackInvocationHandler.invoke(JDKCallbackInvocationHandler.java:91) at $Proxy27.callBack(Unknown Source) at org.apache.tuscany.sca.vtest.javaapi.conversation.callback.custom.impl.BServiceImpl.testCallBack(BServiceImpl.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:109) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108) 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.CallbackInterfaceInterceptor.invoke(CallbackInterfaceInterceptor.java:43) 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 $Proxy26.testCallBack(Unknown Source) at org.apache.tuscany.sca.vtest.javaapi.conversation.callback.custom.impl.AServiceImpl.testCallback(AServiceImpl.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:109) at org.apache.tuscan
[jira] Created: (TUSCANY-2311) Second equivalently typed callback field not injected
Second equivalently typed callback field not injected - Key: TUSCANY-2311 URL: https://issues.apache.org/jira/browse/TUSCANY-2311 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams The Java CAA specification states on lines 670-671: 670 If a single callback has a type that is compatible with multiple declared callback fields, then all of them will 671 be set. The test org.apache.tuscany.sca.vtest.javaapi.conversation.callback.CallbackTestCase.statefulMultiBidirectional() demonstrates that a second annotated field with the same type is not injected. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2306) Client callback state preserved through stateless callback
Client callback state preserved through stateless callback -- Key: TUSCANY-2306 URL: https://issues.apache.org/jira/browse/TUSCANY-2306 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Lines 650-654 of the Java CAA specification state: "The difference for stateless services is that the callback field would not be available if the component is servicing a request for anything other than the original client. So, the technique used in the previous section, where there was a response from the backend Service which was forwarded as a callback from MyService would not work because the *callback field would be null* when the message from the backend system was received." The test case org.apache.tuscany.sca.vtest.javaapi.conversation.callback.CallbackTestCase.statelessCallback3 demosntrates that the callback field is not null when the message is received from the "back end service" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2299) Client-set callback id not preserved on stateless callback
Client-set callback id not preserved on stateless callback -- Key: TUSCANY-2299 URL: https://issues.apache.org/jira/browse/TUSCANY-2299 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams The Java CAA spec says the following re: stateless callbacks: 613 A stateless callback interface is a callback whose interface is not marked as conversational. Unlike 614 stateless services, the client of that uses stateless callbacks will not have callback methods routed to an 615 instance of the client that contains any state that is relevant to the conversation. As such, it is the 616 responsibility of such a client to perform any persistent state management itself. The only information that 617 the client has to work with (other than the parameters of the callback method) is a callback ID object that is 618 passed with requests to the service and is guaranteed to be returned with any callback. 619 The following is a repeat of the client code fragment above, but with the assumption that in this case the 620 MyServiceCallback is stateless. The client in this case needs to set the callback ID before invoking the 621 service and then needs to get the callback ID when the response is received. The test: org.apache.tuscany.sca.vtest.javaapi.conversation.callback.CallbackTestCase.statelessCallback2 demonstrates this issue and is currently @Ignore(d) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2287) Add vtest for @Destroy annotation
[ https://issues.apache.org/jira/browse/TUSCANY-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2287. --- Resolution: Fixed Closing this but would like to see it converted to use the SCADomain APIs for configuring a domain and locating test services from the test client. > Add vtest for @Destroy annotation > - > > Key: TUSCANY-2287 > URL: https://issues.apache.org/jira/browse/TUSCANY-2287 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Vamsavardhana Reddy > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2287-2.patch, TUSCANY-2287-final.patch, > TUSCANY-2287.patch > > > Add verification tests for @Destroy annotation. > Java Common Annotations and APIs v1.00 - Sec 1.8.8 - Lines 1225 to 1227: > 1225 The @Destroy annotation type is used to annotate a Java class method > that will be called when the scope > 1226 defined for the local service implemented by the class ends. The method > must have a void return value and > 1227 no arguments. The annotated method must be public -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2286) Add vtest for @Init annotation
[ https://issues.apache.org/jira/browse/TUSCANY-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2286. --- Resolution: Fixed I am closing this but would like to see the test case converted to use the SCADomain APIs from the test client to locate the services under test. > Add vtest for @Init annotation > -- > > Key: TUSCANY-2286 > URL: https://issues.apache.org/jira/browse/TUSCANY-2286 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Vamsavardhana Reddy > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2286-2.patch, TUSCANY-2286-3.patch, > TUSCANY-2286-final.patch, TUSCANY-2286.patch > > > Add verification tests for @Init annotation. > Java Common Annotations and APIs v1.00 - Section 1.8.11 - Lines 1290 to 1293: > 1290 The @Init annotation type is used to annotate a Java class method that > is called when the scope defined for > 1291 the local service implemented by the class starts. The method must have > a void return value and no > 1292 arguments. The annotated method must be public. The annotated method is > called after all property and > 1293 reference injection is complete. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2286) Add vtest for @Init annotation
[ https://issues.apache.org/jira/browse/TUSCANY-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594329#action_12594329 ] Kevin Williams commented on TUSCANY-2286: - I applied the latest patch OK but there is no associated test case. I assume you did not intend this. > Add vtest for @Init annotation > -- > > Key: TUSCANY-2286 > URL: https://issues.apache.org/jira/browse/TUSCANY-2286 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Vamsavardhana Reddy > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2286-2.patch, TUSCANY-2286-3.patch, > TUSCANY-2286-final.patch, TUSCANY-2286.patch > > > Add verification tests for @Init annotation. > Java Common Annotations and APIs v1.00 - Section 1.8.11 - Lines 1290 to 1293: > 1290 The @Init annotation type is used to annotate a Java class method that > is called when the scope defined for > 1291 the local service implemented by the class starts. The method must have > a void return value and no > 1292 arguments. The annotated method must be public. The annotated method is > called after all property and > 1293 reference injection is complete. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2291) Runtime does not detect illegal mix of local and remoteable on bidirectional interface
Runtime does not detect illegal mix of local and remoteable on bidirectional interface -- Key: TUSCANY-2291 URL: https://issues.apache.org/jira/browse/TUSCANY-2291 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Priority: Minor From Lines 534, 535 of the Java API/Annotaitons spec: Callbacks may be used for both remotable and local services. Either both interfaces of a bidirectional service must be remotable, or both must be local. It is illegal to mix the two. The test org.apache.tuscany.sca.vtest.javaapi.conversation.callback.statefulCallback3 demonstrates this error and is currently @Ignore(d) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2286) Add vtest for @Init annotation
[ https://issues.apache.org/jira/browse/TUSCANY-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593632#action_12593632 ] Kevin Williams commented on TUSCANY-2286: - Thanks for contributing this test for the @init annotation. Unfortunately, I am unable to apply your patch file. The error I get (using TortiseSVN) is : "An unknown line type was found in line 51!" This may have to do with the inclusion of property changes in the patch. I did take a scan through the content and wonder if you could make changes to your patch to be more consistent with the existing tests.? We have been using conventions for service names and components and test structure and I hope to keep this consistent throughout the bucket. We have also been using a javadoc convention on the test cases to explicitly call out the specification line numbers that each test addresses. Thanks again! > Add vtest for @Init annotation > -- > > Key: TUSCANY-2286 > URL: https://issues.apache.org/jira/browse/TUSCANY-2286 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Vamsavardhana Reddy >Assignee: Vamsavardhana Reddy > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2286.patch > > > Add verification tests for @Init annotation. > Java Common Annotations and APIs v1.00 - Section 1.8.11 - Lines 1290 to 1293: > 1290 The @Init annotation type is used to annotate a Java class method that > is called when the scope defined for > 1291 the local service implemented by the class starts. The method must have > a void return value and no > 1292 arguments. The annotated method must be public. The annotated method is > called after all property and > 1293 reference injection is complete. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (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 ] Kevin Williams closed TUSCANY-2284. --- Resolution: Fixed > 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] Assigned: (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 ] Kevin Williams reassigned TUSCANY-2284: --- Assignee: Kevin Williams > 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] Created: (TUSCANY-2283) Conversation should end due to non-business exception
Conversation should end due to non-business exception - Key: TUSCANY-2283 URL: https://issues.apache.org/jira/browse/TUSCANY-2283 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams The Java APIs and Annotations spec states: 487 A conversation ends, and any state associated with the conversation is freed up, when: ... 492 • Any non-business exception is thrown by a conversational operation This is not happening as illustrated by the vtest: org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.LifetimeTestCase.lifetime11 It is currently @Ignore(d) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2282) Poor warning issued when annotating private field with @Callback
Poor warning issued when annotating private field with @Callback Key: TUSCANY-2282 URL: https://issues.apache.org/jira/browse/TUSCANY-2282 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Priority: Minor I inadvertently marked a private field with @Callback and received the following warning: WARNING: Invalid annotation @org.osoa.sca.annotations.Callback(value=class java.lang.Void) is found on private org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.AServiceCallback org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.impl.BServiceImpl.callback I should have realized sooner what the real problem was (private fields cannot be annotated) but a message like: "WARNING: Invalid annotation @org.osoa.sca.annotations.Callback(value=class java.lang.Void) is found on private org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.AServiceCallback org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.impl.BServiceImpl.callback. You must not annotate private fields and if you do then the runtime will ignore them and only give you this warning." I think an exception would be even better since the application will not work without the requested injection. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2276) Conversation not started on reference injection
[ https://issues.apache.org/jira/browse/TUSCANY-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2276. --- Resolution: Fixed Closing because I mis-read the spec. Specifically, line 478 says: "*and* then a method of the service is called." > Conversation not started on reference injection > --- > > Key: TUSCANY-2276 > URL: https://issues.apache.org/jira/browse/TUSCANY-2276 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams > > I have a failing test from this part of the Java API /Annotation > specification: > "475 Conversations start on the client side when one of the following occur: > 476 • A @Reference to a conversational service is injected" > Test tries to access the conversation id from the injected ServiceReference > and finds it to be null. > The test demonstrating this is > org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.LifetimeTestCase.lifetime1 > It is currently @Ignored -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2276) Conversation not started on reference injection
Conversation not started on reference injection --- Key: TUSCANY-2276 URL: https://issues.apache.org/jira/browse/TUSCANY-2276 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams I have a failing test from this part of the Java API /Annotation specification: "475 Conversations start on the client side when one of the following occur: 476 • A @Reference to a conversational service is injected" Test tries to access the conversation id from the injected ServiceReference and finds it to be null. The test demonstrating this is org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.LifetimeTestCase.lifetime1 It is currently @Ignored -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2274) @Scope vTest failing intermittently
@Scope vTest failing intermittently Key: TUSCANY-2274 URL: https://issues.apache.org/jira/browse/TUSCANY-2274 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams The atScope1 vTest fails intermittently like this: --- T E S T S --- Running org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase Setting up Apr 26, 2008 5:00:57 PM org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntime buildComposite WARNING: Can't find monitor extension on the classpath GService->initGService atScope1 Exception in thread "Thread-5" java.lang.IllegalArgumentException: Invalid phase name: component.implementation at org.apache.tuscany.sca.core.invocation.InvocationChainImpl.addInvoker(InvocationChainImpl.java:106) at org.apache.tuscany.sca.core.invocation.InvocationChainImpl.addInvoker(InvocationChainImpl.java:70) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addImplementationInterceptor(RuntimeWireImpl.java:316) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:188) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:109) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChain(RuntimeWireImpl.java:115) at org.apache.tuscany.sca.core.assembly.RuntimeComponentServiceImpl.getInvocationChain(RuntimeComponentServiceImpl.java:120) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.getInvoker(RuntimeSCAReferenceBindingProvider.java:232) ThreadB1->BService2 ThreadB2->BService9 at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.createInvoker(RuntimeSCAReferenceBindingProvider.java:245) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addReferenceBindingInterceptor(RuntimeWireImpl.java:228) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:167) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:109) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.getInvocationChain(JDKInvocationHandler.java:243) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:148) at $Proxy17.setCurrentState(Unknown Source) at org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase$CThread.run(ScopeAnnotationTestCase.java:359) Exception in thread "Thread-4" org.osoa.sca.ServiceUnavailableException: Service not found for component CComponent reference $self$.CService (bi ndingURI=/CComponent operation=getName). Ensure that the composite containing the service is loaded and started somewhere in the SCA domain and t hat if running in a remote node that the interface of the target service marked as @Remotable at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.createInvoker(RuntimeSCAReferenceBindingProvider.java:247) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addReferenceBindingInterceptor(RuntimeWireImpl.java:228) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:167) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:109) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.getInvocationChain(JDKInvocationHandler.java:243) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:148) at $Proxy17.setCurrentState(Unknown Source) at org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase$CThread.run(ScopeAnnotationTestCase.java:359) atScope2 --- Still not clear if this is a runtime r test setup issue. I have added Ignore annotation until this is resolved. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2264) Updates to RequestContext's vtest
[ https://issues.apache.org/jira/browse/TUSCANY-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2264. --- Resolution: Fixed Fix Version/s: Java-SCA-Next > Updates to RequestContext's vtest > - > > Key: TUSCANY-2264 > URL: https://issues.apache.org/jira/browse/TUSCANY-2264 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang >Assignee: Kevin Williams > Fix For: Java-SCA-Next > > Attachments: RequestContextUpdatesJIRA2264.patch > > > Updates to RequestContext test cases. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2263) Updates to Exception's vtest
[ https://issues.apache.org/jira/browse/TUSCANY-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2263. --- Resolution: Fixed Fix Version/s: Java-SCA-Next > Updates to Exception's vtest > > > Key: TUSCANY-2263 > URL: https://issues.apache.org/jira/browse/TUSCANY-2263 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang >Assignee: Kevin Williams > Fix For: Java-SCA-Next > > Attachments: ExceptionUpdatesJIRA2263.patch > > > New and updates to Exception test cases. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2264) Updates to RequestContext's vtest
[ https://issues.apache.org/jira/browse/TUSCANY-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams reassigned TUSCANY-2264: --- Assignee: Kevin Williams > Updates to RequestContext's vtest > - > > Key: TUSCANY-2264 > URL: https://issues.apache.org/jira/browse/TUSCANY-2264 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang >Assignee: Kevin Williams > Attachments: RequestContextUpdatesJIRA2264.patch > > > Updates to RequestContext test cases. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2263) Updates to Exception's vtest
[ https://issues.apache.org/jira/browse/TUSCANY-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams reassigned TUSCANY-2263: --- Assignee: Kevin Williams > Updates to Exception's vtest > > > Key: TUSCANY-2263 > URL: https://issues.apache.org/jira/browse/TUSCANY-2263 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang >Assignee: Kevin Williams > Attachments: ExceptionUpdatesJIRA2263.patch > > > New and updates to Exception test cases. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (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 ] Kevin Williams closed TUSCANY-2257. --- Resolution: Fixed > 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 >Assignee: Kevin Williams >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] Assigned: (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 ] Kevin Williams reassigned TUSCANY-2257: --- Assignee: Kevin Williams > 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 >Assignee: Kevin Williams >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] Closed: (TUSCANY-2249) Updates to ComponentContext's vtest
[ https://issues.apache.org/jira/browse/TUSCANY-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2249. --- Resolution: Fixed Fix Version/s: Java-SCA-Next > Updates to ComponentContext's vtest > --- > > Key: TUSCANY-2249 > URL: https://issues.apache.org/jira/browse/TUSCANY-2249 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang > Fix For: Java-SCA-Next > > Attachments: ComponentContextUpdatesJIRA2249.patch > > > More vtest test cases for ComponentContext API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2247) vtest content for Java API spec - Conversation/Async
[ https://issues.apache.org/jira/browse/TUSCANY-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams reassigned TUSCANY-2247: --- Assignee: Kevin Williams > vtest content for Java API spec - Conversation/Async > - > > Key: TUSCANY-2247 > URL: https://issues.apache.org/jira/browse/TUSCANY-2247 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Assignee: Kevin Williams > > Add vtest content for Java API/Annotation Spec section 1.6 - Conversations > and Async -- 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-2247) vtest content for Java API spec - Conversation/Async
vtest content for Java API spec - Conversation/Async - Key: TUSCANY-2247 URL: https://issues.apache.org/jira/browse/TUSCANY-2247 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Kevin Williams Add vtest content for Java API/Annotation Spec section 1.6 - Conversations and Async -- 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] Closed: (TUSCANY-2244) Updates to ServiceReference's vtest
[ https://issues.apache.org/jira/browse/TUSCANY-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2244. --- Resolution: Fixed Fix Version/s: Java-SCA-Next > Updates to ServiceReference's vtest > --- > > Key: TUSCANY-2244 > URL: https://issues.apache.org/jira/browse/TUSCANY-2244 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang >Assignee: Kevin Williams > Fix For: Java-SCA-Next > > Attachments: ServiceReferenceUpdatesJIRA2244.patch > > > Updates to vtest's test cases for ServiceReference. -- 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] Assigned: (TUSCANY-2244) Updates to ServiceReference's vtest
[ https://issues.apache.org/jira/browse/TUSCANY-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams reassigned TUSCANY-2244: --- Assignee: Kevin Williams > Updates to ServiceReference's vtest > --- > > Key: TUSCANY-2244 > URL: https://issues.apache.org/jira/browse/TUSCANY-2244 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang >Assignee: Kevin Williams > Attachments: ServiceReferenceUpdatesJIRA2244.patch > > > Updates to vtest's test cases for ServiceReference. -- 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] Closed: (TUSCANY-2238) Test Cases for Exception APIs
[ https://issues.apache.org/jira/browse/TUSCANY-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2238. --- Resolution: Fixed Fix Version/s: Java-SCA-Next > Test Cases for Exception APIs > - > > Key: TUSCANY-2238 > URL: https://issues.apache.org/jira/browse/TUSCANY-2238 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang >Assignee: Kevin Williams > Fix For: Java-SCA-Next > > Attachments: ExceptionJIRA2238.patch, ExceptionJIRA2238.zip > > > vtest's test cases for the various Exceptions. -- 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] Assigned: (TUSCANY-2238) Test Cases for Exception APIs
[ https://issues.apache.org/jira/browse/TUSCANY-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams reassigned TUSCANY-2238: --- Assignee: Kevin Williams > Test Cases for Exception APIs > - > > Key: TUSCANY-2238 > URL: https://issues.apache.org/jira/browse/TUSCANY-2238 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang >Assignee: Kevin Williams > Attachments: ExceptionJIRA2238.patch > > > vtest's test cases for the various Exceptions. -- 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-2238) Test Cases for Exception APIs
[ https://issues.apache.org/jira/browse/TUSCANY-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams updated TUSCANY-2238: Component/s: Java SCA Verification Tests > Test Cases for Exception APIs > - > > Key: TUSCANY-2238 > URL: https://issues.apache.org/jira/browse/TUSCANY-2238 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang > Attachments: ExceptionJIRA2238.patch > > > vtest's test cases for the various Exceptions. -- 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] Closed: (TUSCANY-2233) Test Cases for Conversation API
[ https://issues.apache.org/jira/browse/TUSCANY-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2233. --- Resolution: Fixed > Test Cases for Conversation API > --- > > Key: TUSCANY-2233 > URL: https://issues.apache.org/jira/browse/TUSCANY-2233 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang >Assignee: Kevin Williams > Attachments: ConversationJIRA2233.patch, ConversationJIRA2233.zip, > ConversationJIRA2233Updated.patch > > > Conversation's vtest. -- 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] Closed: (TUSCANY-2232) Test Cases for ServiceReference API
[ https://issues.apache.org/jira/browse/TUSCANY-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2232. --- Resolution: Fixed Fix Version/s: Java-SCA-Next > Test Cases for ServiceReference API > --- > > Key: TUSCANY-2232 > URL: https://issues.apache.org/jira/browse/TUSCANY-2232 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang >Assignee: Kevin Williams > Fix For: Java-SCA-Next > > Attachments: ServiceReferenceJIRA2232.patch, > ServiceReferenceJIRA2232.zip, ServiceReferenceJIRA2232Updated.patch > > > ServiceReference's vtest. -- 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] Assigned: (TUSCANY-2233) Test Cases for Conversation API
[ https://issues.apache.org/jira/browse/TUSCANY-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams reassigned TUSCANY-2233: --- Assignee: Kevin Williams > Test Cases for Conversation API > --- > > Key: TUSCANY-2233 > URL: https://issues.apache.org/jira/browse/TUSCANY-2233 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang >Assignee: Kevin Williams > Attachments: ConversationJIRA2233.patch, ConversationJIRA2233.zip, > ConversationJIRA2233Updated.patch > > > Conversation's vtest. -- 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] Closed: (TUSCANY-2231) Test Cases for CallableReference API
[ https://issues.apache.org/jira/browse/TUSCANY-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2231. --- Resolution: Fixed Fix Version/s: Java-SCA-Next > Test Cases for CallableReference API > > > Key: TUSCANY-2231 > URL: https://issues.apache.org/jira/browse/TUSCANY-2231 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang > Fix For: Java-SCA-Next > > Attachments: CallableReferenceJIRA2231.patch, > CallableReferenceJIRA2231.zip, CallableReferenceJIRA2231Updated.patch > > > Test Cases for CallableReference's vtest. -- 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] Assigned: (TUSCANY-2232) Test Cases for ServiceReference API
[ https://issues.apache.org/jira/browse/TUSCANY-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams reassigned TUSCANY-2232: --- Assignee: Kevin Williams > Test Cases for ServiceReference API > --- > > Key: TUSCANY-2232 > URL: https://issues.apache.org/jira/browse/TUSCANY-2232 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang >Assignee: Kevin Williams > Attachments: ServiceReferenceJIRA2232.patch, > ServiceReferenceJIRA2232.zip, ServiceReferenceJIRA2232Updated.patch > > > ServiceReference's vtest. -- 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] Closed: (TUSCANY-2230) Test Cases for RequestContext API
[
https://issues.apache.org/jira/browse/TUSCANY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Williams closed TUSCANY-2230.
---
Resolution: Fixed
I noticed the following empty test method in the RequestContext test case:
/**
* L863
* getServiceReference() - Returns the callable reference that represents
the service or callback reference that the request was invoked on.
* It is illegal for the service implementation to try to call the
setCallback() on a returned service reference.
*
* @throws Exception
*/
@Test
public void testGetServiceReference() throws Exception {
}
Do you intend to come back to this?
> Test Cases for RequestContext API
> -
>
> Key: TUSCANY-2230
> URL: https://issues.apache.org/jira/browse/TUSCANY-2230
> Project: Tuscany
> Issue Type: Test
> Components: Java SCA Verification Tests
>Reporter: Yee-Kang Chang
>Assignee: Kevin Williams
> Attachments: RequestContextJIRA2230.patch,
> RequestContextJIRA2230.zip, RequestContextJIRA2230Updated.patch
>
>
> Test Cases for RequestContext's vtest.
--
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] Assigned: (TUSCANY-2230) Test Cases for RequestContext API
[ https://issues.apache.org/jira/browse/TUSCANY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams reassigned TUSCANY-2230: --- Assignee: Kevin Williams (was: Simon Laws) > Test Cases for RequestContext API > - > > Key: TUSCANY-2230 > URL: https://issues.apache.org/jira/browse/TUSCANY-2230 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang >Assignee: Kevin Williams > Attachments: RequestContextJIRA2230.patch, > RequestContextJIRA2230.zip, RequestContextJIRA2230Updated.patch > > > Test Cases for RequestContext's vtest. -- 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] Closed: (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 ] Kevin Williams closed TUSCANY-2234. --- Resolution: Fixed Fix Version/s: Java-SCA-Next > 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 >Assignee: Kevin Williams >Priority: Minor > Fix For: Java-SCA-Next > > 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] Assigned: (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 ] Kevin Williams reassigned TUSCANY-2234: --- Assignee: Kevin Williams > 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 >Assignee: Kevin Williams >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] Closed: (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 ] Kevin Williams closed TUSCANY-2221. --- Resolution: Fixed Fix Version/s: Java-SCA-Next > 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 > Fix For: Java-SCA-Next > > 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-2199) Tests for @Reference annotation
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 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] Created: (TUSCANY-2195) Test cases for ComponentContext API
Test cases for ComponentContext API --- Key: TUSCANY-2195 URL: https://issues.apache.org/jira/browse/TUSCANY-2195 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Kevin Williams Contributions for ComponentContext API testing can be attached here -- 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] Closed: (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 ] Kevin Williams closed TUSCANY-2188. --- Resolution: Fixed Fix Version/s: Java-SCA-Next > 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 > Fix For: Java-SCA-Next > > 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] Commented: (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=12585208#action_12585208 ] Kevin Williams commented on TUSCANY-2188: - Regarding: "What is the different between interfaces and class ? Are both same?" A service interface can be defined by either a Java Interface or a Java class and the naming default should be the same in either case. So if you used an Interface "x.y.z.Calculator or a Class "x.y.z.Calculator" to define the Service interface then the service name should default to "Calculator" > 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] Commented: (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=12584783#action_12584783 ] Kevin Williams commented on TUSCANY-2188: - Gilbert, this looks great and I just committed your contribution. A few small comments: 1 - I created a jira (T-2191) for the test you have "@ignored". 2 - I reformatted the code based on the Tuscany guidelines. You can find formatting templates for various IDE's here: https://svn.apache.org/repos/asf/incubator/tuscany/java/etc/ 3 - I modified your "atService6" test to make use of junits "fail" feature. I think this is more straightforward. 4 - I am not sure that atService8 is working as intended since I don't see you explicitly use the name of the service. I'll leave this jira open until we resolve #4 Thanks! > 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]
[jira] Created: (TUSCANY-2191) A @Service annotation with no attributes causes exception
A @Service annotation with no attributes causes exception - Key: TUSCANY-2191 URL: https://issues.apache.org/jira/browse/TUSCANY-2191 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Line 1635 of the Java Annotations spec says: A @Service annotation with no attributes is meaningless, it is the same as not having the annotation there at all. However, the presence of the the annotation without attributes results in the following: org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.sca.contribution.service.ContributionResolveException: org.apache.tuscany.sca.implementation.java.introspect.impl.IllegalServiceDefinitionException: No interfaces specified at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:69) -- 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-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=12584742#action_12584742 ] Kevin Williams commented on TUSCANY-2188: - Thanks Gilbert! I'll take a look at this and will probably commit it his afternoon if it checks out. > 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]
[jira] Created: (TUSCANY-2188) New tests for Java @Service annotaion
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 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] Created: (TUSCANY-2165) Java runtime should inject service references to field with common name in absence of @Reference
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 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] Created: (TUSCANY-2145) SCADomain.getService () should throw exception when bogus component name is passed
SCADomain.getService () should throw exception when bogus component name is
passed
--
Key: TUSCANY-2145
URL: https://issues.apache.org/jira/browse/TUSCANY-2145
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-Next
Reporter: Kevin Williams
Priority: Minor
SCADomain.getService() currently returns a proxy even when the component name
passed is not in the domain.
I have created a test (currently "ignored") in the new vTest suite to
demonstrate.
@Test
@Ignore
public void bogusComponentName() throws Exception {
--
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] Reopened: (TUSCANY-2055) ServiceReference.getConversationID() not returning generated conversation IDs
[
https://issues.apache.org/jira/browse/TUSCANY-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Williams reopened TUSCANY-2055:
-
This is from the Java Annotations and API V100-5
521 1.6.6.2. Accessing Conversation IDs from Clients
522Whether the conversation ID is chosen by the client or is generated by
the system, the client may access
523the conversation ID by calling ServiceReference.getConversationID().
Am I misreading this?
> ServiceReference.getConversationID() not returning generated conversation IDs
> -
>
> Key: TUSCANY-2055
> URL: https://issues.apache.org/jira/browse/TUSCANY-2055
> Project: Tuscany
> Issue Type: Bug
> Components: Specification
>Affects Versions: Java-SCA-Next
>Reporter: Kevin Williams
>
> ServiceReference.getConversationID() returns null unless the Conversation ID
> is set by the user.
> This is the current implementaiton:
> public Object getConversationID() {
> return conversationID;
> }
> It seems that that if the cached ID is null, and there is a valid related
> Converasation object then the impl should return the related
> Conversation.getConversationID.
--
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-2055) ServiceReference.getConversationID() not returning generated conversation IDs
[
https://issues.apache.org/jira/browse/TUSCANY-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573160#action_12573160
]
Kevin Williams commented on TUSCANY-2055:
-
The getConversationID() test in
src\test\java\org\apache\tuscany\sca\itest\conversational\ConversationLifetimeTestCase.java
demonstrates this bug. It is currently annotated it it with @Ignore
> ServiceReference.getConversationID() not returning generated conversation IDs
> -
>
> Key: TUSCANY-2055
> URL: https://issues.apache.org/jira/browse/TUSCANY-2055
> Project: Tuscany
> Issue Type: Bug
> Components: Specification
>Affects Versions: Java-SCA-Next
>Reporter: Kevin Williams
>
> ServiceReference.getConversationID() returns null unless the Conversation ID
> is set by the user.
> This is the current implementaiton:
> public Object getConversationID() {
> return conversationID;
> }
> It seems that that if the cached ID is null, and there is a valid related
> Converasation object then the impl should return the related
> Conversation.getConversationID.
--
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-2055) ServiceReference.getConversationID() not returning generated conversation IDs
ServiceReference.getConversationID() not returning generated conversation IDs
-
Key: TUSCANY-2055
URL: https://issues.apache.org/jira/browse/TUSCANY-2055
Project: Tuscany
Issue Type: Bug
Components: Specification
Affects Versions: Java-SCA-Next
Reporter: Kevin Williams
ServiceReference.getConversationID() returns null unless the Conversation ID is
set by the user.
This is the current implementaiton:
public Object getConversationID() {
return conversationID;
}
It seems that that if the cached ID is null, and there is a valid related
Converasation object then the impl should return the related
Conversation.getConversationID.
--
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] Closed: (TUSCANY-1354) SCADomain. getService () should follow CompositeContext.getService() conventions for "service-name"
[
https://issues.apache.org/jira/browse/TUSCANY-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Williams closed TUSCANY-1354.
---
Resolution: Won't Fix
Canceling since the current behavior seems in-line with the 1.0 specifications
> SCADomain. getService () should follow CompositeContext.getService()
> conventions for "service-name"
> ---
>
> Key: TUSCANY-1354
> URL: https://issues.apache.org/jira/browse/TUSCANY-1354
> Project: Tuscany
> Issue Type: Bug
>Affects Versions: Java-SCA-M2
>Reporter: Kevin Williams
> Fix For: Java-SCA-Next
>
>
> The current SCADomain method
> "public abstract B getService(Class businessInterface, String
> serviceName);"
> is similar in purpose to the .95 specification for
> CompositeContext.locateService API. For this reason, the new API should
> follow the conventions established of the old API.
> This is from the .95 specification:
> public interface CompositeContext {
> ...
> T locateService(Class serviceType, String serviceName);
> }
> "serviceName" can take on one of the following forms:
> /
> If the service-name is not provided, the name of the serviceType sans package
> name will be used as the service-name
> The current implementation getService ends up in the following code:
> public ServiceReference getServiceReference(Class
> businessInterface, String name) {
> // Extract the component name
> String componentName;
> String serviceName;
> int i = name.indexOf('/');
> if (i != -1) {
> componentName = name.substring(0, i);
> serviceName = name.substring(i + 1);
> } else {
> componentName = name;
> serviceName = null;
> }
> It seems that the "else" should default serviceName to
> businessInterface.getSimpleName() in order to follow the existing convention.
> A test case will follow shortly.
--
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-1354) SCADomain. getService () should follow CompositeContext.getService() conventions for "service-name"
SCADomain. getService () should follow CompositeContext.getService()
conventions for "service-name"
---
Key: TUSCANY-1354
URL: https://issues.apache.org/jira/browse/TUSCANY-1354
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-M2
Reporter: Kevin Williams
Fix For: Java-SCA-Next
The current SCADomain method
"public abstract B getService(Class businessInterface, String
serviceName);"
is similar in purpose to the .95 specification for
CompositeContext.locateService API. For this reason, the new API should follow
the conventions established of the old API.
This is from the .95 specification:
public interface CompositeContext {
...
T locateService(Class serviceType, String serviceName);
}
"serviceName" can take on one of the following forms:
/
If the service-name is not provided, the name of the serviceType sans package
name will be used as the service-name
The current implementation getService ends up in the following code:
public ServiceReference getServiceReference(Class businessInterface,
String name) {
// Extract the component name
String componentName;
String serviceName;
int i = name.indexOf('/');
if (i != -1) {
componentName = name.substring(0, i);
serviceName = name.substring(i + 1);
} else {
componentName = name;
serviceName = null;
}
It seems that the "else" should default serviceName to
businessInterface.getSimpleName() in order to follow the existing convention.
A test case will follow shortly.
--
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-1347) IndexOutOfBoundsException thrown when trying to locate a service that includes a callback
IndexOutOfBoundsException thrown when trying to locate a service that includes a callback - Key: TUSCANY-1347 URL: https://issues.apache.org/jira/browse/TUSCANY-1347 Project: Tuscany Issue Type: Bug Components: Java SCA Embedded Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Fix For: Java-SCA-Next More complete description and test case to follow Here is the exception thrown... [6/14/07 17:59:55:187 MDT] 0020 SystemErr R java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:572) at java.util.ArrayList.get(ArrayList.java:347) at org.apache.tuscany.sca.core.runtime.RuntimeComponentImpl.getServiceReference(RuntimeComponentImpl.java:98) at org.apache.tuscany.sca.core.runtime.RuntimeComponentImpl.createSelfReference(RuntimeComponentImpl.java:58) at org.apache.tuscany.sca.host.embedded.impl.EmbeddedSCADomain.getServiceReference(EmbeddedSCADomain.java:292) at org.apache.tuscany.sca.host.embedded.impl.EmbeddedSCADomain.getService(EmbeddedSCADomain.java:228) at org.apache.tuscany.sca.host.embedded.impl.SimpleCompositeContextImpl.locateService(SimpleCompositeContextImpl.java:80) at sca.fvt.EchoServiceImpl.asyncEcho(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) -- 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] Closed: (TUSCANY-1087) DAS should not commit individual commands as part of applyChanges
[ https://issues.apache.org/jira/browse/TUSCANY-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-1087. --- Resolution: Fixed Verified in revision: 502521 > DAS should not commit individual commands as part of applyChanges > - > > Key: TUSCANY-1087 > URL: https://issues.apache.org/jira/browse/TUSCANY-1087 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Affects Versions: Java-DAS-Mx >Reporter: Kevin Williams > Fix For: Java-DAS-Mx > > > The DAS must commit all commands resulting from ChangeSummary processing as > an atomic unit. > Sam Su's original note: > "Hi kevin, thanks for you response. > I debuged the application in Eclipse, I was sure that after user1 was > inserted into database without an exception, a commit was performed on the > connection. > as two data objects needed to be inserted into database in my program, from > the DAS source code, DAS will produce two different InsertCommandImpl > instances for these two changes.The 'success' flag is in two different > command instance, furthermore, it's a method scope variable, it can not be > shared between two command instances. When command instance for user1 > execute without an exception, it will proceed to perform a commit on the > connection, command instance for user2 execute will throw an exception, so > rollback. However the use1 has been already commited to database although > use2 fail to be inserted into database." > I have added a test "TransactionTests.estReadModifyApply()" t hat > demonstrates this defect. -- 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-1088) SDO should tolerate malformed XML
[ https://issues.apache.org/jira/browse/TUSCANY-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams updated TUSCANY-1088: Description: I had some off-line discussion with Frank and Yang. Here is the summary: As an improvement to consumability, SDO should tolerate some malformed XML. XML documents are often less than well-formed. Rather than failing on deserialization when a document does not completely conform to its schema, we should consider making some assumptions and continuing on. Some competitor technologies do this today. Here's an example. Say we have this schema: http://QuickTest/HelloWorld"; xmlns:tns="http://QuickTest/HelloWorld"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified"> If we get an xml that looks like this: http://QuickTest/HelloWorld"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://QuickTest/HelloWorld HelloWorldMessage.xsd "> input1 then we will fail validating this since input1 isn't fully qualified. Here's the xml that would work: http://QuickTest/HelloWorld"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://QuickTest/HelloWorld HelloWorldMessage.xsd "> tns:input1 Frank mentioned 2 potential approaches: 1. Read the element in as if it was an open content property. If you reserialize it would be the same (still invalid). 2. If a property with the same name (but different namespace) exists, then associate it with that. When you reserialize it will be then be correct. The later seems the best approach. Yang also contributed the following: It's friendly to tolerate if a user forgets to qualify a local element. There're 3 scenarios may not have the same elementFormDefault="qualified" enforcement policy. What do you think? 3-1.http://QuickTest/HelloWorld";> input1 The author may have forgot to qualify "input1" element, although "input1" may also be a global element without NameSpace. It's friendly to tolerate. 3-2.http://QuickTest/HelloWorld"; xmlns:onPurpose="differentNameSpace"> input1 The author has qualified "input1" element; I'm not confident we should tolerate. 3-3.http://QuickTest/HelloWorld"; xmlns="differentNameSpace"> input1 It's hard to tell if the author may have forgot to qualify "input1" element or not. I bet on not. Should we tolerate? was: I had some off-line discussion with Frank and Yang. Here is the summary: As an improvement to consumability, SDO should tolerate some malformed XML. It is not uncommon for XML documents to not be less than well-formed. Rather than failing on deserialization when a document does not completely conform to its schema, we should consider making some assumptions and continuing on. Some competitor technologies do this today. Here's an example. Say we have this schema: http://QuickTest/HelloWorld"; xmlns:tns="http://QuickTest/HelloWorld"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified"> If we get an xml that looks like this: http://QuickTest/HelloWorld"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://QuickTest/HelloWorld HelloWorldMessage.xsd "> input1 then we will fail validating this since input1 isn't fully qualified. Here's the xml that would work: http://QuickTest/HelloWorld"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://QuickTest/HelloWorld HelloWorldMessage.xsd "> tns:input1 Frank mentioned 2 potential approaches: 1. Read the element in as if it was an open content property. If you reserialize it would be the same (still invalid). 2. If a property with the same name (but different namespace) exists, then associate it with that. When you reserialize it will be then be correct. The later seems the best approach. Yang also contributed the following: It's friendly to tolerate if a user forgets to qualify a local element. There're 3 scenarios may not have the same elementFormDefault="qualified" enforcement policy. What do you think? 3-1.http://QuickTest/HelloWorld";> input1 The author may have forgot to qualify "input1" element, although "input1" may also be a global element without NameSpace. It's friendly to tolerate. 3-2.http://QuickTest/HelloWorld"; xmlns:onPurpose="differentNameSpace"> input1 The author has quali
[jira] Created: (TUSCANY-1088) SDO should tolerate malformed XML
SDO should tolerate malformed XML - Key: TUSCANY-1088 URL: https://issues.apache.org/jira/browse/TUSCANY-1088 Project: Tuscany Issue Type: Improvement Components: Java SDO Implementation Affects Versions: Java-SDO-Mx Reporter: Kevin Williams Fix For: Java-SDO-Mx I had some off-line discussion with Frank and Yang. Here is the summary: As an improvement to consumability, SDO should tolerate some malformed XML. It is not uncommon for XML documents to not be less than well-formed. Rather than failing on deserialization when a document does not completely conform to its schema, we should consider making some assumptions and continuing on. Some competitor technologies do this today. Here's an example. Say we have this schema: http://QuickTest/HelloWorld"; xmlns:tns="http://QuickTest/HelloWorld"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified"> If we get an xml that looks like this: http://QuickTest/HelloWorld"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://QuickTest/HelloWorld HelloWorldMessage.xsd "> input1 then we will fail validating this since input1 isn't fully qualified. Here's the xml that would work: http://QuickTest/HelloWorld"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://QuickTest/HelloWorld HelloWorldMessage.xsd "> tns:input1 Frank mentioned 2 potential approaches: 1. Read the element in as if it was an open content property. If you reserialize it would be the same (still invalid). 2. If a property with the same name (but different namespace) exists, then associate it with that. When you reserialize it will be then be correct. The later seems the best approach. Yang also contributed the following: It's friendly to tolerate if a user forgets to qualify a local element. There're 3 scenarios may not have the same elementFormDefault="qualified" enforcement policy. What do you think? 3-1.http://QuickTest/HelloWorld";> input1 The author may have forgot to qualify "input1" element, although "input1" may also be a global element without NameSpace. It's friendly to tolerate. 3-2.http://QuickTest/HelloWorld"; xmlns:onPurpose="differentNameSpace"> input1 The author has qualified "input1" element; I'm not confident we should tolerate. 3-3.http://QuickTest/HelloWorld"; xmlns="differentNameSpace"> input1 It's hard to tell if the author may have forgot to qualify "input1" element or not. I bet on not. Should we tolerate? -- 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-1087) DAS should not commit individual commands as part of applyChanges
DAS should not commit individual commands as part of applyChanges - Key: TUSCANY-1087 URL: https://issues.apache.org/jira/browse/TUSCANY-1087 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Affects Versions: Java-DAS-Mx Reporter: Kevin Williams Fix For: Java-DAS-Mx The DAS must commit all commands resulting from ChangeSummary processing as an atomic unit. Sam Su's original note: "Hi kevin, thanks for you response. I debuged the application in Eclipse, I was sure that after user1 was inserted into database without an exception, a commit was performed on the connection. as two data objects needed to be inserted into database in my program, from the DAS source code, DAS will produce two different InsertCommandImpl instances for these two changes.The 'success' flag is in two different command instance, furthermore, it's a method scope variable, it can not be shared between two command instances. When command instance for user1 execute without an exception, it will proceed to perform a commit on the connection, command instance for user2 execute will throw an exception, so rollback. However the use1 has been already commited to database although use2 fail to be inserted into database." I have added a test "TransactionTests.estReadModifyApply()" t hat demonstrates this defect. -- 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-1027) DAS should throw a meaningful exception if applyChanges process encounters a DO with no defined PK
DAS should throw a meaningful exception if applyChanges process encounters a DO with no defined PK -- Key: TUSCANY-1027 URL: https://issues.apache.org/jira/browse/TUSCANY-1027 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Affects Versions: Java-M3 Reporter: Kevin Williams Fix For: Java-M3 Currrently a NPE is thrown while processing a changed DO that has no defined PK. A more meaninful exception should be thrown instead. DefectTests.testReadUpdateWithNoPKColumns() demonstrates this problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-1007) ApplyChnages fails when added DO does not include a modified property
ApplyChnages fails when added DO does not include a modified property - Key: TUSCANY-1007 URL: http://issues.apache.org/jira/browse/TUSCANY-1007 Project: Tuscany Issue Type: Bug Reporter: Kevin Williams Looks like the generated insert is invalid when the change history for an added DO does not include a modified property. I think the correct behavior should be to generate an ID-only INSERT. An alternative would be to generate an INSERT that initializes all columns ... i'd be interested in hearing arguments to justify the latter. This test: /das/src/test/java/org/apache/tuscany/das/rdb/test/CrudWithChangeHistory.testReadInsertApply() demonstrates the problem. I have temporarily commented it out. Here is the stack trace: java.lang.RuntimeException: SQL Exception: Column 'ID' cannot accept a NULL value. at org.apache.tuscany.das.rdb.impl.InsertCommandImpl.execute(InsertCommandImpl.java:47) at org.apache.tuscany.das.rdb.impl.ChangeOperation.execute(ChangeOperation.java:73) at org.apache.tuscany.das.rdb.impl.Changes.execute(Changes.java:57) at org.apache.tuscany.das.rdb.impl.ApplyChangesCommandImpl.execute(ApplyChangesCommandImpl.java:69) at org.apache.tuscany.das.rdb.impl.DASImpl.applyChanges(DASImpl.java:244) at org.apache.tuscany.das.rdb.test.CrudWithChangeHistory.testReadInsertApply(CrudWithChangeHistory.java:289) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:23) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: SQL Exception: Column 'ID' cannot accept a NULL value. at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source) at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown Source) at org.apache.tuscany.das.rdb.impl.Statement.executeUpdate(Statement.java:173) at org.apache.tuscany.das.rdb.impl.Statement.executeUpdate(Statement.java:133) at org.apache.tuscany.das.rdb.impl.InsertCommandImpl.execute(InsertCommandImpl.java:44) ... 28 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-986) DAS integration with SDO 2.1 APIs
DAS integration with SDO 2.1 APIs - Key: TUSCANY-986 URL: http://issues.apache.org/jira/browse/TUSCANY-986 Project: Tuscany Issue Type: Improvement Components: Java DAS RDB Affects Versions: Java-Mx Reporter: Kevin Williams Fix For: Java-Mx The DAS is using function provided by SDOUtils that should be replaced by SDO 2.1 APIs as they become available. Helper Context TypeHelper, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-957) DAS generates invalid INSERT statement when no properties are set on the new DO
DAS generates invalid INSERT statement when no properties are set on the new DO
---
Key: TUSCANY-957
URL: http://issues.apache.org/jira/browse/TUSCANY-957
Project: Tuscany
Issue Type: Bug
Components: Java DAS RDB
Affects Versions: Java-Mx
Reporter: Kevin Williams
Fix For: Java-Mx
If a new DO is created but no properties are set then the DAS generates an
invalid INSERT statement that looks something like this:
"insert into COMPANY( values ("
The following test case (added to
/das/src/test/java/org/apache/tuscany/das/rdb/test/GeneratedId.java)
illustrates this bug:
/**
* Test insert into row with generated ID and no attributes set
*/
public void testInsert5() throws Exception {
DAS das = DAS.FACTORY.createDAS(getConfig("CompanyConfig.xml"),
getConnection());
Command select = das.getCommand("all companies");
DataObject root = select.executeQuery();
root.createDataObject("COMPANY");
das.applyChanges(root);
// Verify insert
root = select.executeQuery();
assertEquals(4, root.getList("COMPANY").size());
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-952) DAS must support queries that reference tables in different "schemas"
[ http://issues.apache.org/jira/browse/TUSCANY-952?page=comments#action_12454468 ] Kevin Williams commented on TUSCANY-952: Dev list thread here: http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg11282.html > DAS must support queries that reference tables in different "schemas" > - > > Key: TUSCANY-952 > URL: http://issues.apache.org/jira/browse/TUSCANY-952 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Affects Versions: Java-Mx >Reporter: Kevin Williams > Fix For: Java-Mx > > > The DAS is curently ignorant of database schema designations. This means the > DAS will generate incorrect write statements when it processes the change > summary from a data graph that originated from a query that uses schema names > that are different from the default schema. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-953) Invalid data graph results in NPE on applyChanges
Invalid data graph results in NPE on applyChanges - Key: TUSCANY-953 URL: http://issues.apache.org/jira/browse/TUSCANY-953 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Affects Versions: Java-Mx Reporter: Kevin Williams Fix For: Java-Mx Jeff Watkins reports that sending a single DataObject to applyChanges results in an NPE. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-952) DAS must support queries that reference tables in different "schemas"
DAS must support queries that reference tables in different "schemas" - Key: TUSCANY-952 URL: http://issues.apache.org/jira/browse/TUSCANY-952 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Affects Versions: Java-Mx Reporter: Kevin Williams Fix For: Java-Mx The DAS is curently ignorant of database schema designations. This means the DAS will generate incorrect write statements when it processes the change summary from a data graph that originated from a query that uses schema names that are different from the default schema. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-939) DAS Should throw an exception when ResultSetMetadata is invalid
[ http://issues.apache.org/jira/browse/TUSCANY-939?page=comments#action_12452067 ] Kevin Williams commented on TUSCANY-939: Wojtek's issue should be incorporated as part of this JIRA. He tried to port a DAS sample to Oracle from Derby with the result that queries produced empty graphs. This was corrected by adding explicit result shape descriptors in the config but an infromative exception should have been thrown when the DAS detected the lack of good ResultSetMetadata as well as no explicit shape description in the config. > DAS Should throw an exception when ResultSetMetadata is invalid > --- > > Key: TUSCANY-939 > URL: http://issues.apache.org/jira/browse/TUSCANY-939 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Affects Versions: Java-Mx >Reporter: Kevin Williams >Priority: Minor > Fix For: Java-Mx > > > This test seems to have strayed from its original purpose. > C:\apacheSVN\java\das\rdb\src\test\java\org\apache\tuscany\das\rdb\test\ResultSetShapeTests.java > "testReadSingleVerifyShapeUse" > The query used intentionally produces invalid ResultSetMetadata and there is > no ResultSetShape specified to override its use by the DAS. Since the test > assumes the ResultSetMetadata is invalid, I would expect the DAS to throw and > exception rather than return an invalid data graph which it seems to be doing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-885) Property DataObject.getProperty(String propertyName) should return null if the property cannot be found
[ http://issues.apache.org/jira/browse/TUSCANY-885?page=all ] Kevin Williams updated TUSCANY-885: --- Attachment: DAS_885.txt This patch is to convert the single DAS test case that depends on IllegalArgumentException. It shoud be applied at the same time to avoid a build break. > Property DataObject.getProperty(String propertyName) should return null if > the property cannot be found > --- > > Key: TUSCANY-885 > URL: http://issues.apache.org/jira/browse/TUSCANY-885 > Project: Tuscany > Issue Type: Bug > Components: Java SDO Implementation >Affects Versions: Java-Mx >Reporter: Fuhwei Lwo > Assigned To: Kelvin Goodson >Priority: Minor > Fix For: Java-Mx > > Attachments: DAS_885.txt, tuscany-885.patch > > > Based on SDO 2.01 specification, DataObject.getProperty(String propertyName) > should return null if the property cannot be found. Unfortunately, it > returns IlegalArgumentException now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-948) Consider DAS config connection info for J2SE environment
Consider DAS config connection info for J2SE environment Key: TUSCANY-948 URL: http://issues.apache.org/jira/browse/TUSCANY-948 Project: Tuscany Issue Type: Improvement Components: Java DAS RDB Affects Versions: Java-Mx Reporter: Kevin Williams Fix For: Java-Mx Currently the DAS allow users to specfify a JDBC Connection for the DAS to utilize by either providing a JDBC Connection explicitly or provifing a JNDI name in the config file. We should reconsider allowing DriverManager info to be provided to allow similar, config-based set up, in a J2SE enviroinment. I know this was debated in the past but I cannot recall if this was deferred or rejected. The issues may have been around the need to include user/password info in the DriverManager info. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-542) Pager API needs some work
[ http://issues.apache.org/jira/browse/TUSCANY-542?page=all ] Kevin Williams reassigned TUSCANY-542: -- Assignee: Kevin Williams > Pager API needs some work > - > > Key: TUSCANY-542 > URL: http://issues.apache.org/jira/browse/TUSCANY-542 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Affects Versions: Java-Mx >Reporter: Kevin Williams > Assigned To: Kevin Williams > Fix For: Java-Mx > > > We need to decide on the scenarios envisioned for this disconnected paging > capability and adjust the API to fit those scenarios. If the main scenario > is something similar to a paged web search then the pager instance should > probably be very lightweight (storable in session). Currently, the pager is > heavy since it holds a conection instance. > We also should add a pager create method on DAS (or DASFactory) to be > consistent. Our tests currently just new up an impl. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-939) DAS Should throw an exception when ResultSetMetadata is invalid
DAS Should throw an exception when ResultSetMetadata is invalid --- Key: TUSCANY-939 URL: http://issues.apache.org/jira/browse/TUSCANY-939 Project: Tuscany Issue Type: Improvement Components: Java DAS RDB Affects Versions: Java-Mx Reporter: Kevin Williams Priority: Minor Fix For: Java-Mx This test seems to have strayed from its original purpose. C:\apacheSVN\java\das\rdb\src\test\java\org\apache\tuscany\das\rdb\test\ResultSetShapeTests.java "testReadSingleVerifyShapeUse" The query used intentionally produces invalid ResultSetMetadata and there is no ResultSetShape specified to override its use by the DAS. Since the test assumes the ResultSetMetadata is invalid, I would expect the DAS to throw and exception rather than return an invalid data graph which it seems to be doing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-885) Property DataObject.getProperty(String propertyName) should return null if the property cannot be found
[ http://issues.apache.org/jira/browse/TUSCANY-885?page=all ] Kevin Williams updated TUSCANY-885: --- Priority: Blocker (was: Minor) > Property DataObject.getProperty(String propertyName) should return null if > the property cannot be found > --- > > Key: TUSCANY-885 > URL: http://issues.apache.org/jira/browse/TUSCANY-885 > Project: Tuscany > Issue Type: Bug > Components: Java SDO Implementation >Affects Versions: Java-Mx >Reporter: Fuhwei Lwo > Assigned To: Kelvin Goodson >Priority: Blocker > Fix For: Java-Mx > > Attachments: tuscany-885.patch > > > Based on SDO 2.01 specification, DataObject.getProperty(String propertyName) > should return null if the property cannot be found. Unfortunately, it > returns IlegalArgumentException now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (TUSCANY-885) Property DataObject.getProperty(String propertyName) should return null if the property cannot be found
[ http://issues.apache.org/jira/browse/TUSCANY-885?page=all ] Kevin Williams reopened TUSCANY-885: Brent pointed out that the DAS test case is valid and seems to be exposing a problem with the patch associated with this JIRA: "The issue is that you can't call getList() with a property name that does not exist. When the code is changed to throw null, some upstream code in the getList() implementation will return the parent DataObject rather than null, eventually resulting in a ClassCastException. I'm going to re-enable the test and change the property to something like "nonExistantProperty" to make this clearer. " > Property DataObject.getProperty(String propertyName) should return null if > the property cannot be found > --- > > Key: TUSCANY-885 > URL: http://issues.apache.org/jira/browse/TUSCANY-885 > Project: Tuscany > Issue Type: Bug > Components: Java SDO Implementation >Affects Versions: Java-Mx >Reporter: Fuhwei Lwo > Assigned To: Kelvin Goodson >Priority: Minor > Fix For: Java-Mx > > Attachments: tuscany-885.patch > > > Based on SDO 2.01 specification, DataObject.getProperty(String propertyName) > should return null if the property cannot be found. Unfortunately, it > returns IlegalArgumentException now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-915) User level documentation
[ http://issues.apache.org/jira/browse/TUSCANY-915?page=all ] Kevin Williams updated TUSCANY-915: --- Work has started here: http://wiki.apache.org/ws/Tuscany/TuscanyJava/DAS_Java_Overview/RDBDAS_Java_User_Guide > User level documentation > > > Key: TUSCANY-915 > URL: http://issues.apache.org/jira/browse/TUSCANY-915 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS Documentation >Affects Versions: Java-Mx >Reporter: Kevin Williams > Fix For: Java-Mx > > > User level documentation for major DAS features -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-915) User level documentation
[ http://issues.apache.org/jira/browse/TUSCANY-915?page=all ] Kevin Williams updated TUSCANY-915: --- Component/s: Java DAS Documentation (was: Java DAS RDB) Description: User level documentation for major DAS features (was: Need user level documentation for major DAS features) > User level documentation > > > Key: TUSCANY-915 > URL: http://issues.apache.org/jira/browse/TUSCANY-915 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS Documentation >Affects Versions: Java-Mx >Reporter: Kevin Williams > Fix For: Java-Mx > > > User level documentation for major DAS features -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-916) OCC recovery framework
OCC recovery framework -- Key: TUSCANY-916 URL: http://issues.apache.org/jira/browse/TUSCANY-916 Project: Tuscany Issue Type: New Feature Components: Java DAS RDB Affects Versions: Java-Mx Reporter: Kevin Williams Fix For: Java-Mx A framework to assist client in recovering from optimistic collision failures -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-915) User level documentation
User level documentation Key: TUSCANY-915 URL: http://issues.apache.org/jira/browse/TUSCANY-915 Project: Tuscany Issue Type: Improvement Components: Java DAS RDB Affects Versions: Java-Mx Reporter: Kevin Williams Fix For: Java-Mx Need user level documentation for major DAS features -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-900) samples/testing/tomcat/datasource.xsl missing ASF header
[ http://issues.apache.org/jira/browse/TUSCANY-900?page=all ] Kevin Williams closed TUSCANY-900. -- Fix Version/s: Java-Mx (was: Java-M2) Resolution: Fixed > samples/testing/tomcat/datasource.xsl missing ASF header > > > Key: TUSCANY-900 > URL: http://issues.apache.org/jira/browse/TUSCANY-900 > Project: Tuscany > Issue Type: Bug > Components: Java DAS Samples >Affects Versions: Java-M2 >Reporter: Luciano Resende > Assigned To: Luciano Resende >Priority: Blocker > Fix For: Java-Mx > > Attachments: tuscany900-lresende.20061106.txt > > > See details here : > http://www.mail-archive.com/general%40incubator.apache.org/msg11407.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-899) DAS Config model should declare a global element named "Config"
[ http://issues.apache.org/jira/browse/TUSCANY-899?page=all ] Kevin Williams closed TUSCANY-899. -- Fix Version/s: Java-Mx Resolution: Fixed Verified with revision: 470494 > DAS Config model should declare a global element named "Config" > --- > > Key: TUSCANY-899 > URL: http://issues.apache.org/jira/browse/TUSCANY-899 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Reporter: Frank Budinsky > Assigned To: Kevin Williams > Fix For: Java-Mx > > > You should add a "Config" global element declaration to config.xsd: > > Doing this, however, will cause all your instance documents to fail when > loading. The reason is because the instance documents currently use > xsiNoNamespaceSchemaLocation as a hack to make it work without the "proper" > global element defined: > xsi:noNamespaceSchemaLocation="http:///org.apache.tuscany.das.rdb/config.xsd"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > ... > > The xsi:noNamespaceSchemaLocation needs to be removed and replace with > xmlns="http:///org.apache.tuscany.das.rdb/config.xsd"; instead. > One more change, to make it all work properly, is that you need to add > elementFormDefault="qualified" in config.xsd, otherwise the nested elements > won't be found when loading. > To summarize, you need to add elementFormDefault and global element to > config.xsd. With these changes config.xsd should look something like this: > xmlns:config="http:///org.apache.tuscany.das.rdb/config.xsd"; >xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >targetNamespace="http:///org.apache.tuscany.das.rdb/config.xsd"; >elementFormDefault="qualified"> > > >... > All the instance files, e.g., CompanyConfig.xml, need to be changed so that > the root element uses xmlns instead of xsi:noNamespaceSchemaLocation. The > instance documents should all look something like this: > http:///org.apache.tuscany.das.rdb/config.xsd";> > ... > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-899) DAS Config model should declare a global element named "Config"
[ http://issues.apache.org/jira/browse/TUSCANY-899?page=all ] Kevin Williams reassigned TUSCANY-899: -- Assignee: Kevin Williams > DAS Config model should declare a global element named "Config" > --- > > Key: TUSCANY-899 > URL: http://issues.apache.org/jira/browse/TUSCANY-899 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Reporter: Frank Budinsky > Assigned To: Kevin Williams > > You should add a "Config" global element declaration to config.xsd: > > Doing this, however, will cause all your instance documents to fail when > loading. The reason is because the instance documents currently use > xsiNoNamespaceSchemaLocation as a hack to make it work without the "proper" > global element defined: > xsi:noNamespaceSchemaLocation="http:///org.apache.tuscany.das.rdb/config.xsd"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > ... > > The xsi:noNamespaceSchemaLocation needs to be removed and replace with > xmlns="http:///org.apache.tuscany.das.rdb/config.xsd"; instead. > One more change, to make it all work properly, is that you need to add > elementFormDefault="qualified" in config.xsd, otherwise the nested elements > won't be found when loading. > To summarize, you need to add elementFormDefault and global element to > config.xsd. With these changes config.xsd should look something like this: > xmlns:config="http:///org.apache.tuscany.das.rdb/config.xsd"; >xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >targetNamespace="http:///org.apache.tuscany.das.rdb/config.xsd"; >elementFormDefault="qualified"> > > >... > All the instance files, e.g., CompanyConfig.xml, need to be changed so that > the root element uses xmlns instead of xsi:noNamespaceSchemaLocation. The > instance documents should all look something like this: > http:///org.apache.tuscany.das.rdb/config.xsd";> > ... > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-865) DAS sample distribution does not include sample canned database
[ http://issues.apache.org/jira/browse/TUSCANY-865?page=all ] Kevin Williams resolved TUSCANY-865. Resolution: Fixed Verified with revision: 464963 > DAS sample distribution does not include sample canned database > --- > > Key: TUSCANY-865 > URL: http://issues.apache.org/jira/browse/TUSCANY-865 > Project: Tuscany > Issue Type: Bug > Components: Java DAS Samples >Affects Versions: Java-M2 >Reporter: Luciano Resende > Assigned To: Luciano Resende >Priority: Blocker > Fix For: Java-M2 > > Attachments: readme.htm, tuscany865.lresende.20061017.txt > > > Currently, the sample distribution is not including the dastest caned sample > db. > See thread below for more information: >http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg09750.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-841) Need a test for relationships formed by compound keys
Need a test for relationships formed by compound keys - Key: TUSCANY-841 URL: http://issues.apache.org/jira/browse/TUSCANY-841 Project: Tuscany Issue Type: Improvement Components: Java DAS RDB Affects Versions: Java-Mx Reporter: Kevin Williams Fix For: Java-Mx There are no tests in the current suite that exercise relationships formed by compound keys. We need to add this for completeness. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-835) "Version" column should default to "managed = true"
"Version" column should default to "managed = true" --- Key: TUSCANY-835 URL: http://issues.apache.org/jira/browse/TUSCANY-835 Project: Tuscany Issue Type: Improvement Components: Java DAS RDB Affects Versions: Java-Mx Reporter: Kevin Williams Fix For: Java-Mx This is fine with me. Most of the time users will probably want to have the DAS do the work rather than manually updating the version column or having a database trigger do it. Brent On 10/12/06, Kevin Williams <[EMAIL PROTECTED]> wrote: > While writing the User level documentation for Optimistic Concurrency > Control I started wondering about our current default which is to NOT > manage the designated version column. That is, we assume that it is the > client's responsibility to modify this column whenever they modify any > other column in the associated row. > > We also provide another option in which the DAS is responsible for > bumping the value of the designated column whenever any other column is > modified in the associated row. It seems to me that this will be the > typical case and should also be the default to save the developer from > specifying another piece of config. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-820) Configuration info for Command Parameters should include an "index"
[ http://issues.apache.org/jira/browse/TUSCANY-820?page=all ] Kevin Williams updated TUSCANY-820: --- Component/s: Java DAS RDB Description: The configuration for command parameters should include an index. As an example, the current SP example with an OUT parameter has the following associated config file: http:///org.apache.tuscany.das.rdb/config.xsd"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> In keeping with our philosophy that only config that needs to vary from the defaults should be provided, the first parameter should not need to be defined since it is of the default IN type. However, removing the first parameter definition results in the following error. java.lang.RuntimeException: SQL Exception: Parameter 1 cannot be registered as an OUT parameter because it is an IN parameter. at org.apache.tuscany.das.rdb.impl.SPCommandImpl.executeQuery(SPCommandImpl.java:73) at org.apache.tuscany.das.rdb.test.StoredProcs.testGetNamedCustomers(StoredProcs.java:116) I assume this error is caused by the runtime inferring index positionally from the config input and the first parameter is necessary as a place holder in order for the OUT parameter to properly have an index of 2. was: The configuration for command parameters should include an index. As an example, the current SP example with an OUT parameter has the following associated config file: http:///org.apache.tuscany.das.rdb/config.xsd"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> In keeping with our philosophy that only config that needs to vary from the defaults should be provided, the first parameter should not need to be defined since it is of the default IN type. However, removing the first parameter definition results in the following error. java.lang.RuntimeException: SQL Exception: Parameter 1 cannot be registered as an OUT parameter because it is an IN parameter. at org.apache.tuscany.das.rdb.impl.SPCommandImpl.executeQuery(SPCommandImpl.java:73) at org.apache.tuscany.das.rdb.test.StoredProcs.testGetNamedCustomers(StoredProcs.java:116) I assume this error is caused by the runtime inferring index positionally from the config input and the first parameter is necessary as a place holder in order for the OUT parameter to properly have an index of 2. > Configuration info for Command Parameters should include an "index" > --- > > Key: TUSCANY-820 > URL: http://issues.apache.org/jira/browse/TUSCANY-820 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Affects Versions: Java-Mx >Reporter: Kevin Williams > Fix For: Java-Mx > > > The configuration for command parameters should include an index. As an > example, the current SP example with an OUT parameter has the following > associated config file: > xsi:noNamespaceSchemaLocation="http:///org.apache.tuscany.das.rdb/config.xsd"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > kind="procedure"> > > > > > In keeping with our philosophy that only config that needs to vary from the > defaults should be provided, the first parameter should not need to be > defined since it is of the default IN type. However, removing the first > parameter definition results in the following error. > > java.lang.RuntimeException: SQL Exception: Parameter 1 cannot be registered > as an OUT parameter because it is an IN parameter. > at > org.apache.tuscany.das.rdb.impl.SPCommandImpl.executeQuery(SPCommandImpl.java:73) > at > org.apache.tuscany.das.rdb.test.StoredProcs.testGetNamedCustomers(StoredProcs.java:116) > > I assume this error is caused by the runtime inferring index positionally > from the config input and the first parameter is necessary as a place holder > in order for the OUT parameter to properly have an index of 2. > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-820) Configuration info for Command Parameters should include an "index"
Configuration info for Command Parameters should include an "index" --- Key: TUSCANY-820 URL: http://issues.apache.org/jira/browse/TUSCANY-820 Project: Tuscany Issue Type: Improvement Affects Versions: Java-Mx Reporter: Kevin Williams Fix For: Java-Mx The configuration for command parameters should include an index. As an example, the current SP example with an OUT parameter has the following associated config file: http:///org.apache.tuscany.das.rdb/config.xsd"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> In keeping with our philosophy that only config that needs to vary from the defaults should be provided, the first parameter should not need to be defined since it is of the default IN type. However, removing the first parameter definition results in the following error. java.lang.RuntimeException: SQL Exception: Parameter 1 cannot be registered as an OUT parameter because it is an IN parameter. at org.apache.tuscany.das.rdb.impl.SPCommandImpl.executeQuery(SPCommandImpl.java:73) at org.apache.tuscany.das.rdb.test.StoredProcs.testGetNamedCustomers(StoredProcs.java:116) I assume this error is caused by the runtime inferring index positionally from the config input and the first parameter is necessary as a place holder in order for the OUT parameter to properly have an index of 2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-814) Update DAS binary distribution with updated legal files and new documentation files
[ http://issues.apache.org/jira/browse/TUSCANY-814?page=all ] Kevin Williams resolved TUSCANY-814. Resolution: Fixed > Update DAS binary distribution with updated legal files and new documentation > files > --- > > Key: TUSCANY-814 > URL: http://issues.apache.org/jira/browse/TUSCANY-814 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Affects Versions: Java-M2 >Reporter: Luciano Resende > Assigned To: Luciano Resende > Fix For: Java-M2 > > Attachments: tuscany814.lresende.20061009.zip > > > Update DAS binary distribution with updated legal files and new documentation > files -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
