Re: [jira] Commented: (TUSCANY-2383) Cannot define component property with Component Type File
Well Mike, you broke a working test! :-) I tried your suggestion and initializing the property via the component type file does not seem to work. I opened T-2390. --Kevin On Thu, Jun 12, 2008 at 4:12 PM, Mike Edwards <[EMAIL PROTECTED]> wrote: > Raymond Feng wrote: >> >> Hi, >> >> I just make the protected field injectable. :-) >> >> Thanks, >> Raymond > > Folks, > > Unless I've got the wrong end of the stick, you should be able to derive a > test to check that the property declaration from the componentType file IS > being used, by setting a default value for the property in the componentType > file only - and checking that this value is actually used in the code at > runtime (eg have a getter method for it which the testcase uses to extract > the value). > > > Yours, Mike. >
[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.
Re: [jira] Commented: (TUSCANY-2383) Cannot define component property with Component Type File
I may not fully understand your comment but it seems inconsistent to support the provision of component type information via a type file for service and reference elements but not for property elements. In the test I have only removed the @Property annotation from the java implementation and replaced it with an element in the Component Type File. On Thu, Jun 12, 2008 at 10:52 AM, Raymond Feng (JIRA) wrote: > >[ > https://issues.apache.org/jira/browse/TUSCANY-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604572#action_12604572 > ] > > Raymond Feng commented on TUSCANY-2383: > --- > > If the component is implemented in java, I think this is a grey area in the > spec. The spec says the configuration in the componentType should be > compatible with the result from the instrospection of implemention. Let's say > your purpose is to declare a property in the componentType file, then it has > to be associated to a field or setter in the java class. Is the field/setter > required to be protected or public? My understanding is that we can use the > componentType to provide a default value to a property, but not "add" a new > property if it doesn't exist in the impl class. > > There are discussions on the ML about if we should use componentType to > redefine the service interface using interface.wsdl. I think these are in the > same area. > >> 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. > >
Re: Good practice for disabling/ignoring failing test cases
Since the vtest script assumes a test comment structure around
specification line numbers, I created a new script specific to this
purpose and added it to /java/etc. It scans for files named
*testCase.java and collects methods annotated with @Ignore.
I could use some help getting this automated but, in the meantime,
I'll run this scan weekly and post results to the dev-list
Here is output from tonight's scan:
-
Content generated by from C:/tuscanysvn/java/sca
Test case files scanned 2008-06-11 (svn:Revision: 663374)
* Total files processed = 591
* Total ingnored test cases = 26
The following test cases have ignored test methods ...
org.apache.tuscany.sca.itest.databindings.jaxb.DatabindingTestCase
testWSMap() , no associated jira
testWSHashMap() , no associated jira
org.apache.tuscany.sca.itest.databindings.jaxb.PrimitivesDatabindingTestCase
testSCANegateByteArray() , T-2351
testWSNegateByteArray() , T-2349
org.apache.tuscany.sca.itest.references.ManualWiredReferenceTestCase
testD2Reference() , no associated jira
client.CatalogEJBClientTestCase
testCatalogEJB() , no associated jira
org.apache.tuscany.sca.vtest.assembly.ctypefile.CompomnentTypeFileTestCase
typeFile3() , T-2383
org.apache.tuscany.sca.vtest.javaapi.annotations.conversationattributes.ConversationAttributesAnnotationTestCase
singlePrincipal() , no associated jira
org.apache.tuscany.sca.vtest.javaapi.annotations.property.PropertyAnnotationTestCase
atProperty7() , T-2289
org.apache.tuscany.sca.vtest.javaapi.annotations.reference.ReferenceAnnotationTestCase
bogusComponentName() , no associated jira
org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase
atScope1() , T-2274
atScope7() , no associated jira
org.apache.tuscany.sca.vtest.javaapi.apis.componentcontext.ComponentContextTestCase
testGetRequestContext() , no associated jira
testServiceLookup() , no associated jira
org.apache.tuscany.sca.vtest.javaapi.apis.exception.ExceptionTestCase
testServiceUnavailableException() , no associated jira
org.apache.tuscany.sca.vtest.javaapi.apis.requestcontext.RequestContextTestCase
testGetSecuritySubject() , no associated jira
org.apache.tuscany.sca.vtest.javaapi.conversation.callback.CallbackTestCase
statefulMixedCallback() , T-2291
statelessCallback3() , T-2306
customCallback() , T-2312
org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.LifetimeTestCase
lifetime2() , T-2243
lifetime11() , T-2283
org.apache.tuscany.sca.vtest.wsbinding.nowsdl.multisoapbindings.GeneratedWSDLTestCase
testMultiSoapBindings4() , no associated jira
org.apache.tuscany.sca.vtest.wsbinding.nowsdl.soapversion.GeneratedWSDLTestCase
testSoapVersion4() , no associated jira
testSoapVersion5() , no associated jira
org.apache.tuscany.sca.vtest.wsbinding.WsdlEndpointTestCase
testWsdlEndpoint() , no associated jira
org.apache.tuscany.sca.vtest.wsbinding.WsdlServiceTestCase
testWsdlService() , T-2298
On Wed, Jun 11, 2008 at 6:42 PM, Jean-Sebastien Delfino
<[EMAIL PROTECTED]> wrote:
> Simon Laws wrote:
>>
>> On Wed, Jun 11, 2008 at 6:43 PM, Vamsavardhana Reddy <[EMAIL PROTECTED]>
>> wrote:
>>
>>> Thanks Raymond for pointing this out. We never used this strategy in
>>> Geronimo (infact, I have never put any JIRA number in any of the source
>>> files other that Release Notes may be). I have come across this in
>>> Tuscany
>>> source code and have been following it consistently from then on. Should
>>> give credit to who ever started this in Tuscany :)
>>>
>>> ++Vamsi
>>>
>>> On Wed, Jun 11, 2008 at 11:02 PM, Raymond Feng <[EMAIL PROTECTED]>
>>> wrote:
>>>
Hi,
I see Vamsi uses the following strategy to disable failing unit test
>>>
>>> cases.
@Test
@Ignore("TUSCANY-") // Ignore the test case due to JIRA TUSCANY-
public void testMySrtuff() {
}
I think it's a very good practice we should follow to maintain a clean
build while keep track of the ignored failing test cases with JIRAs.
Thanks,
Raymond
>>
>> +1 good idea
>>
>> Simon
>>
>
> +1
>
> --
> Jean-Sebastien
>
[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.
Re: Good practice for disabling/ignoring failing test cases
The vtest contributors get credit for this pattern! :-) We also have
a Ruby script that scans the test source and, among other things,
lists ignored tests and the associated blocking Jiras.
On Wed, Jun 11, 2008 at 11:49 AM, Simon Laws <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 11, 2008 at 6:43 PM, Vamsavardhana Reddy <[EMAIL PROTECTED]>
> wrote:
>
>> Thanks Raymond for pointing this out. We never used this strategy in
>> Geronimo (infact, I have never put any JIRA number in any of the source
>> files other that Release Notes may be). I have come across this in Tuscany
>> source code and have been following it consistently from then on. Should
>> give credit to who ever started this in Tuscany :)
>>
>> ++Vamsi
>>
>> On Wed, Jun 11, 2008 at 11:02 PM, Raymond Feng <[EMAIL PROTECTED]>
>> wrote:
>>
>> > Hi,
>> >
>> > I see Vamsi uses the following strategy to disable failing unit test
>> cases.
>> >
>> > @Test
>> > @Ignore("TUSCANY-") // Ignore the test case due to JIRA TUSCANY-
>> > public void testMySrtuff() {
>> > }
>> >
>> > I think it's a very good practice we should follow to maintain a clean
>> > build while keep track of the ignored failing test cases with JIRAs.
>> >
>> > Thanks,
>> > Raymond
>> >
>>
>
> +1 good idea
>
> Simon
>
[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.
Re: [NOTICE] Scott Kurz voted as Tuscany committer
Congratulations Scott! --Kevin On Mon, Jun 9, 2008 at 10:50 AM, Antollini, Mario <[EMAIL PROTECTED]> wrote: > Congrats Scott. Welcome! > Mario > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ant > elder > Sent: Monday, June 09, 2008 4:49 AM > To: tuscany-dev > Subject: [NOTICE] Scott Kurz voted as Tuscany committer > > The Tuscany PMC has voted for Scott Kurz to become a Tuscany committer. > > Welcome Scott! > > ...ant >
[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.
Re: [NOTICE] Vamsavardhana Reddy voted as Tuscany committer
Great news Vamsi! Welcome. On Mon, Jun 2, 2008 at 1:20 PM, Simon Laws <[EMAIL PROTECTED]> wrote: > On Mon, Jun 2, 2008 at 8:18 PM, Raymond Feng <[EMAIL PROTECTED]> wrote: > >> Congratulations! You are well deserved. >> >> Thanks, >> Raymond >> >> -- >> From: "Vamsavardhana Reddy" <[EMAIL PROTECTED]> >> Sent: Monday, June 02, 2008 11:15 AM >> To: ; <[EMAIL PROTECTED]> >> Subject: Re: [NOTICE] Vamsavardhana Reddy voted as Tuscany committer >> >> >> Thank you for this great news. And thanks to Tuscany PMC for this >>> recognition. >>> >>> ++Vamsi >>> >>> On Mon, Jun 2, 2008 at 11:32 PM, ant elder <[EMAIL PROTECTED]> wrote: >>> >>> The Tuscany PMC has voted for Vamsavardhana Reddy to become a Tuscany committer. Congratulations and welcome! ...ant > Welcome Vamsi. Very well deserved. > > Simon >
Proposed vtest content for website
I would like to add a vtest section to our website that explains the purpose and structure of the subproject and also provides current specification<->test method mapping info. I have added the proposed content on our staging wiki here: http://cwiki.apache.org/confluence/x/J1MB I welcome any feedback or concerns about this proposed new material for the website. Thanks, --Kevin
Re: cwiki down?
Its back up! Thanks. On Thu, May 29, 2008 at 12:44 PM, Luciano Resende <[EMAIL PROTECTED]> wrote: > It looks like... > > http://monitoring.apache.org/status/ > > On Thu, May 29, 2008 at 11:41 AM, Kevin Williams <[EMAIL PROTECTED]> wrote: >> I am unable to get to: >> http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Home and it >> fails with "502 Proxy Error". Anyone else seeing this? >> -- >> Kevin >> > > > > -- > Luciano Resende > Apache Tuscany Committer > http://people.apache.org/~lresende > http://lresende.blogspot.com/ >
cwiki down?
I am unable to get to: http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Home and it fails with "502 Proxy Error". Anyone else seeing this? -- Kevin
[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.
Re: vtest exception handling
Since the runtime does not provide a spec-compliant API for non-SCA clients to look up services, vtest test clients should now be using the vtest-provided ServiceFinder wrapper class. There is a small handful of vtests still using the Tuscany-specific APIs such as those provided by SCADomain and SCANode2Factory but the plan is to eventually move those to the wrapper class as well after some issues specific to those test cases are resolved. Let me know if I did not answer your question. -- Kevin On Fri, May 23, 2008 at 10:32 AM, ant elder <[EMAIL PROTECTED]> wrote: > I've not done much with the vtests before but looking at TUSCANY-2291 i > wondered if there's a consistent way the vtests should handle testing > exceptions? The CallbackTestCase currently uses ServiceFinder class from > vtest utilities but other vtests that do exceptions like destroy test handle > everything themselves and use the new SCANode2Factory code. Is there a > "standard" way vtests should be doing this? > > ...ant >
[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.
XMLDoclet
Hi Everyone, I would like to produce an XML version of the javadoc output so I can more easily process it further. Has anyone had experience with the maven jellydoc plugin XMLDoclet? Thanks, --Kevin
[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
Re: [VOTE] Graduate Apache Tuscany as a Top Level Project (take two)
And mine... +1 On Sat, May 10, 2008 at 1:57 PM, Mike Edwards <[EMAIL PROTECTED]> wrote: > Folks, > > Here is my +1 > > Yours, Mike. > > ant elder wrote: >> >> Restarting the graduation vote with the updated proposal words, please >> vote >> on the proposal below to graduate Tuscany to a TLP. >> >> +1 from me. >> >> ...ant >> >> X. Establish the Apache Tuscany Project >> >> WHEREAS, the Board of Directors deems it to be in the best >> interests of the Foundation and consistent with the Foundation's >> purpose to establish a Project Management Committee charged with >> the creation and maintenance of open-source software for >> distribution at no charge to the public, that simplifies the >> development, deployment and management of distributed applications >> built as compositions of service components. These components >> may be implemented with a range of technologies and connected >> using a variety of communication protocols. This software will >> implement relevant open standards including, but not limited to, >> the Service Component Architecture standard defined by the OASIS >> OpenCSA member section, and related technologies. >> >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management >> Committee (PMC), to be known as the "Apache Tuscany Project", >> be and hereby is established pursuant to Bylaws of the >> Foundation; and be it further >> >> RESOLVED, that the Apache Tuscany Project be and hereby is >> responsible for the creation and maintenance of software >> related to Apache Tuscany; >> and be it further >> >> RESOLVED, that the office of "Vice President, Apache Tuscany" be >> and hereby is created, the person holding such office to >> serve at the direction of the Board of Directors as the chair >> of the Apache Tuscany Project, and to have primary responsibility >> for management of the projects within the scope of >> responsibility of the Apache Tuscany Project; and be it further >> >> RESOLVED, that the persons listed immediately below be and >> hereby are appointed to serve as the initial members of the >> Apache Tuscany Project: >> >>* Adriano Crestani >>* ant elder >>* Brady Johnson >>* Frank Budinsky >>* Ignacio Silva-Lepe >>* Jean-Sebastien Delfino >>* kelvin goodson >>* Luciano Resende >>* Mark Combellack >>* Matthieu Riou >>* Mike Edwards >>* Paul Fremantle >>* Pete Robbins >>* Raymond Feng >>* Simon Laws >>* Simon Nash >>* Venkata Krishnan >> >> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ant Elder >> be appointed to the office of Vice President, Apache Tuscany, to >> serve in accordance with and subject to the direction of the >> Board of Directors and the Bylaws of the Foundation until >> death, resignation, retirement, removal or disqualification, >> or until a successor is appointed; and be it further >> >> RESOLVED, that the Apache Tuscany Project be and hereby >> is tasked with the migration and rationalization of the Apache >> Incubator Tuscany podling; and be it further >> >> RESOLVED, that all responsibilities pertaining to the Apache >> Incubator Tuscany podling encumbered upon the Apache Incubator >> Project are hereafter discharged. >> > >
[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.
Re: [jira] Commented: (TUSCANY-2306) Client callback state preserved through stateless callback
You are too fast for me! Just checked in revision 654629 On Thu, May 8, 2008 at 3:25 PM, Simon Nash (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/TUSCANY-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595393#action_12595393 > ] > > Simon Nash commented on TUSCANY-2306: > - > > I don't see the statelessCallback3 test in CallbackTestCase.java. What is > the revision number for the checkin? > > > 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-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.
[vtest] @init, @destroy configuration and service lookup
Vamsi, Thanks for your contribution to the vtest bucket for @Init and @Destroy annotations. Can you say why you do not use the SCADomain APIs to configure the domain and locate services from the test client? I would like to keep this pattern consistent throughout the entire suite. -- Kevin
[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.
Re: [VOTE] Graduate Apache Tuscany as a Top Level Project
+1 from me too. On Mon, Apr 28, 2008 at 12:29 PM, Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote: > +1 > > ++Vamsi > > > > On Mon, Apr 28, 2008 at 11:46 PM, ant elder <[EMAIL PROTECTED]> wrote: > > > We've done a lot of work since last October. We now have a diverse > > community > > of contributors and have demonstrated the ability to attract new > > committers > > to create an even more diverse community, we have shown we can do releases > > based on Apache guidelines, and we have shown we conduct our discussions > > in > > public within full view of the community and can resolve disagreements on > > the lists. I think we're ready, so please vote on the proposal below to > > graduate Tuscany to a TLP. > > > > +1 from me. > > > > ...ant > > > > X. Establish the Apache Tuscany Project > > > > WHEREAS, the Board of Directors deems it to be in the best > > interests of the Foundation and consistent with the Foundation's > > purpose to establish a Project Management Committee charged with > > the creation and maintenance of open-source software that > > simplifies the development and deployment of service oriented > > applications and provides a managed service-oriented runtime > > based on the standards defined by the OASIS OpenCSA group, > > for distribution at no charge to the public. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > > Committee (PMC), to be known as the "Apache Tuscany Project", > > be and hereby is established pursuant to Bylaws of the > > Foundation; and be it further > > > > RESOLVED, that the Apache Tuscany Project be and hereby is > > responsible for the creation and maintenance of software > > related to Apache Tuscany; > > and be it further > > > > RESOLVED, that the office of "Vice President, Apache Tuscany" be > > and hereby is created, the person holding such office to > > serve at the direction of the Board of Directors as the chair > > of the Apache Tuscany Project, and to have primary responsibility > > for management of the projects within the scope of > > responsibility of the Apache Tuscany Project; and be it further > > > > RESOLVED, that the persons listed immediately below be and > > hereby are appointed to serve as the initial members of the > > Apache Tuscany Project: > > > > - Adriano Crestani > > - ant elder > > - Brady Johnson > > - Frank Budinsky > > - Ignacio Silva-Lepe > > - Jean-Sebastien Delfino > > - kelvin goodson > > - Luciano Resende > > - Mark Combellack > > - Matthieu Riou > > - Mike Edwards > > - Paul Fremantle > > - Pete Robbins > > - Raymond Feng > > - Simon Laws > > - Simon Nash > > - Venkata Krishnan > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ant Elder > > be appointed to the office of Vice President, Apache Tuscany, to > > serve in accordance with and subject to the direction of the > > Board of Directors and the Bylaws of the Foundation until > > death, resignation, retirement, removal or disqualification, > > or until a successor is appointed; and be it further > > > > RESOLVED, that the Apache Tuscany Project be and hereby > > is tasked with the migration and rationalization of the Apache > > Incubator Tuscany podling; and be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache > > Incubator Tuscany podling encumbered upon the Apache Incubator > > Project are hereafter discharged. > > >
[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.
Error on commit
I am receiving the following when trying to commit: C:\tuscanysvn\java\sca\vtest\java-api\conversation>svn commit -m "First conversation lifetime testcase" svn: Commit failed (details follow): svn: MKACTIVITY of '/repos/asf/!svn/act/e7bafbee-7404-e14a-8c00-eeaf64af1923': 403 Forbidden (https://svn.apache.org) Any ideas what my problem is? Thanks, --Kevin
[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.
Re: [vtest] getCompositeContext API for non-SCA clients
My interest here is centered around a specification-compliant means for non-SCA clients to get access to SAC services. The Java API/Annotation specification suggests that non-SCA client use ComponentContext.getService(Class businessInterface, String referenceName). How a non-SCA client gets the ComponentContext is left up to the implementation. This is a weak area of the spec which is probably why we have the alternative SCADomain.getService(). --Kevin On Thu, Apr 24, 2008 at 2:41 PM, Yee-Kang Chang <[EMAIL PROTECTED]> wrote: > Thanks, Scott, Ant. I think both could work. Perhaps we can start with > getComponentContext(String componentURI) and go from there? > > I gather a client will typically connect to a domain first and then work > with its components? If so, adding getComponentContext() to SCADomain can > be a good start? > > -- > > Kevin, Yee-Kang, > > Did you envision creating a new API that would accept a component URI as > input, > e.g.: > ComponentContext getComponentContext(String componentURI); > > Or were you talking about some sort of virtual component like Ant > mentioned? > Scott > > > > > On Thu, Apr 24, 2008 at 10:49 AM, ant elder <[EMAIL PROTECTED]> wrote: > > Ok, although with non-SCA clients which component would that be? Does > there > > need to be a new something like implementation.web but for JSE clients? > or > > could there be a "virtual" component that has references for all the > > toplevel component services in the domain (which is kind of what we have > > now > > with SCADomain.getService right?). > > > > ...ant > > > > On Thu, Apr 17, 2008 at 9:10 PM, Yee-Kang Chang <[EMAIL PROTECTED]> > > wrote: > > > > > Just thought to follow-up to see if we will do this .. > > > > > > Perhaps SCADomain can be extended to return the ComponentContext for a > > > particular component? > > > > > > Thanks. > > > > > > On Wed, Apr 2, 2008 at 6:37 PM, Kevin Williams > <[EMAIL PROTECTED]> > > > wrote: > > > > The current JUnit tests (iTest and vTest) make use of the > non-standard > > > > SCADomain.getService API to get a handle to an SCA service. Are > there > > > > any plans to provide an API to get a ComponentContext as outlined by > > > > the SCA Java Annotations and APIs specification? I would like to > > > > stick to stick to specified APIs as much as possible in vTest. > > > > > > > > > > > > 1.4.2.1. ComponentContext > > > > Non-SCA client code can use the ComponentContext API to perform > > > > operations against a component in an > > > > SCA domain. How client code obtains a reference to a > ComponentContext > > > > is runtime specific. The following > > > > example demonstrates the use of the component Context API by non-SCA > > > code: > > > > > > > >ComponentContext context = // obtained through host > > > > environment-specific means > > > > > > > >HelloService helloService = > > > > context.getService(HelloService.class,"HelloService"); > > > > > > > > Thanks. > > > > -- > > > > Kevin > > > > > > I don't remember any discussion about this so i guess there are "no > > plans" > > > yet to change it. I agree it seems like we should though. > > > > > > ...ant
Re: [vTest] Test design for ConversationAttributes.SinglePrincipal
I am getting errors during SCADomain initialization:
org.osoa.sca.ServiceRuntimeException:
org.osoa.sca.ServiceRuntimeException:
org.apache.tuscany.sca.contribution.service.ContributionResolveException:
PolicyValidation exception when processing implementation of component
'AComponent' due to Policy Intent
'{http://tuscany.apache.org/xmlns/sca/1.0}jaasAuthentication' is not
defined in this domain
at
org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:276)
at
org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:70)
at
org.apache.tuscany.sca.vtest.javaapi.annotations.conversationattributes.SinglePricipalTestCase.init(SinglePricipalTestCase.java:48)
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)
It seems this is related to warnings received during processing of the
Definitions.xml:
Apr 24, 2008 11:55:22 AM
org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor
read
WARNING: Element
{http://tuscany.apache.org/xmlns/sca/1.0}jaasAuthentication cannot be
processed. ([row,col,system-id]:
[28,9,"file:/C:/tuscanysvn/java/sca/vtest/java-api/annotations/conversationattributes/target/classes/definitions.xml"])
Apr 24, 2008 11:55:22 AM
org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor
read
WARNING: Element
{http://tuscany.apache.org/xmlns/sca/1.0}configurationName cannot be
processed. ([row,col,system-id]:
[29,13,"file:/C:/tuscanysvn/java/sca/vtest/java-api/annotations/conversationattributes/target/classes/definitions.xml"])
Apr 24, 2008 11:55:22 AM
org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor
read
WARNING: Element
{http://tuscany.apache.org/xmlns/sca/1.0}callbackHandler cannot be
processed. ([row,col,system-id]:
[30,13,"file:/C:/tuscanysvn/java/sca/vtest/java-api/annotations/conversationattributes/target/classes/definitions.xml"])
Cleaning up
Here is my definitions file:
http://www.osoa.org/xmlns/sca/1.0";
targetNamespace="http://tuscany.apache.org/xmlns/sca/1.0";
xmlns:sca="http://www.osoa.org/xmlns/sca/1.0";
xmlns:tuscany="http://tuscany.apache.org/xmlns/sca/1.0";
xmlns:convatt="http://convatt";>
http://www.osoa.org/xmlns/sca/1.0";>
AService
org.apache.tuscany.sca.vtest.javaapi.annotations.conversationattributes.security.ACallbackHandler
I have patterned this test after the Calculator-policy sample but I
think I am missing some piece of configuration. Any help is
appreciated.
Thanks,
--Kevin
On Thu, Apr 24, 2008 at 8:30 AM, Kevin Williams <[EMAIL PROTECTED]> wrote:
> I am adding a test to verify @ConversationalAttributes
> (SinglePrincipal = true). Here is the related text from the Java
> API/Annot specification:
>
> 1669 • singlePrincipal (optional) – If true, only the principal
> (the user) that started the conversation has
> 1670 authority to continue the conversation. The default value is false
>
> I would like to create the simplest test possible and this is what I
> have come up with so far:
>
>--Three components each with a single service: A, B, C. C is
> conversational with SinglePrincipal = true.
>--A and B are configured such that each "requires" a policy set
> (jassAuthentication1 and jassAuthentication2 respectively)
>--A will initiate a conversation with C
>--A will pass its C-reference to B
>--B will attempt to continue the conversation and this should fail
> since B represents a different "principal"
>
> I'll start implementing this but would appreciate any suggestions ...
> especially if I am way out in the weeds :-)
>
> Thanks,
>
> --Kevin
>
[vTest] Test design for ConversationAttributes.SinglePrincipal
I am adding a test to verify @ConversationalAttributes (SinglePrincipal = true). Here is the related text from the Java API/Annot specification: 1669 • singlePrincipal (optional) – If true, only the principal (the user) that started the conversation has 1670 authority to continue the conversation. The default value is false I would like to create the simplest test possible and this is what I have come up with so far: --Three components each with a single service: A, B, C. C is conversational with SinglePrincipal = true. --A and B are configured such that each "requires" a policy set (jassAuthentication1 and jassAuthentication2 respectively) --A will initiate a conversation with C --A will pass its C-reference to B --B will attempt to continue the conversation and this should fail since B represents a different "principal" I'll start implementing this but would appreciate any suggestions ... especially if I am way out in the weeds :-) Thanks, --Kevin
[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.
Re: Vtests failing in latest builds?
I reported an intermittent failure like this a few days ago. Are you seeing this consistently? -- Kevin On Tue, Apr 22, 2008 at 5:12 PM, Mike Edwards <[EMAIL PROTECTED]> wrote: > Folks, > > I'm getting a vtest failure in my latest builds - any explanation? > > --- > T E S T S > --- > Running > org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTe > stCase > atScope1 - Setting up > 22-Apr-2008 23:59:30 > org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntim > e buildComposite > WARNING: Can't find monitor extension on the classpath > GService->initGService > Exception in thread "Thread-3" 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.addImplementatio > nInterceptor(RuntimeWireImpl.java:316) > at > org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationCh > ains(RuntimeWireImpl.java:188) > at > org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationCha > ins(RuntimeWireImpl.java:109) > at > org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationCha > in(RuntimeWireImpl.java:115) > at > org.apache.tuscany.sca.core.assembly.RuntimeComponentServiceImpl.getI > nvocationChain(RuntimeComponentServiceImpl.java:120) > at > org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingPro > vider.getInvoker(RuntimeSCAReferenceBindingProvider.java:232) > at > org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingPro > vider.createInvoker(RuntimeSCAReferenceBindingProvider.java:245) > at > org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addReferenceBind > ingInterceptor(RuntimeWireImpl.java:228) > at > org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationCh > ains(RuntimeWireImpl.java:167) > at > org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationCha > ins(RuntimeWireImpl.java:109) > at > org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.getInvoca > tionChain(JDKInvocationHandler.java:243) > at > org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD > KInvocationHandler.java:148) > at $Proxy17.setCurrentState(Unknown Source) > at > org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotatio > nTestCase$CThread.run(ScopeAnnotationTestCase.java:311) > Exception in thread "Thread-4" org.osoa.sca.ServiceUnavailableException: > Service > not found for component CComponent reference $self$.CService > (bindingURI=/CComp > onent operation=getName). Ensure that the composite containing the service > is lo > aded and started somewhere in the SCA domain and that if running in a > remote nod > e that the interface of the target service marked as @Remotable > at > org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingPro > vider.createInvoker(RuntimeSCAReferenceBindingProvider.java:247) > at > org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addReferenceBind > ingInterceptor(RuntimeWireImpl.java:228) > at > org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationCh > ains(RuntimeWireImpl.java:167) > at > org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationCha > ins(RuntimeWireImpl.java:109) > at > org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.getInvoca > tionChain(JDKInvocationHandler.java:243) > at > org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD > KInvocationHandler.java:148) > at $Proxy17.setCurrentState(Unknown Source) > at > org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotatio > nTestCase$CThread.run(ScopeAnnotationTestCase.java:311) > ThreadB1->BService2 > ThreadB2->BService9 > atScope1 - Cleaning up > GService->destroyGService > atScope2 - Setting up > 22-Apr-2008 23:59:31 > org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntim > e buildComposite > WARNING: Can't find monitor extension on the classpath > GService->initGService > DService1->initDService > ThreadD0->DService1 > DService2->initDService > ThreadD1->DService2 > DService3->initDService > ThreadD2->DService3 > DService4->initDService > ThreadD3->DService4 > DService5->initDService > ThreadD4->DService5 > atScope2 - Cleaning up > GService->destroyGService > > atScope3 - Setting up > 22-Apr-2008 23:59:31 > org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntim > e buildComposite > WARNING: Can't find monitor extension on the classpath > GService->in
[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]
[vtest] Java API Spec - Section 2 - Policy Annotations
We are moving through the Java API and Annotations specification pretty well in vTest and I am wondering if we should start on section 2 which covers policy annotations. Are we supporting this section of the specification? -- Kevin - 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]
Re: [jira] Updated: (TUSCANY-2238) Test Cases for Exception APIs
Hi YK, Your patch files always seem to include duplicate entries. On Wed, Apr 16, 2008 at 3:19 PM, Yee-Kang Chang (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/TUSCANY-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Yee-Kang Chang updated TUSCANY-2238: > > > Attachment: ExceptionJIRA2238.patch > > > Test Cases for Exception APIs > > - > > > > Key: TUSCANY-2238 > > URL: https://issues.apache.org/jira/browse/TUSCANY-2238 > > Project: Tuscany > > Issue Type: Test > >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] > > - 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]
[vtest] Intermittent failures with @Scope tests
I am seeing an infrequent, intermittent failure in one of the @Scope vtests: GService->destroyGService Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.281 sec <<< FAILURE! atScope1(org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase) Time elapsed: 1.203 sec <<< FAILURE! junit.framework.ComparisonFailure: null expected:<[None]> but was:<[Unknown]> at junit.framework.Assert.assertEquals(Assert.java:81) at junit.framework.Assert.assertEquals(Assert.java:87) at org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase.atScope1(ScopeAnnotationTestCase.java:93) 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.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75) at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36) at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) 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.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879) Results : Failed tests: atScope1(org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase) Tests run: 5, Failures: 1, Errors: 0, Skipped: 0 --- Has anyone else seen this? -- Kevin - 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]
Re: [jira] Commented: (TUSCANY-2230) Test Cases for RequestContext API
I ran into this same problem last night when trying to apply this patch. I wonder if YK's patch tool is having trouble with adds. I remember the Subclipse tooling having a similar issue. As a workaround, I have found zip files of entirely new folders to be easy to integrate and commit. -- Kevin On Wed, Apr 16, 2008 at 8:23 AM, Simon Laws (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/TUSCANY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589572#action_12589572 > ] > > Simon Laws commented on TUSCANY-2230: > - > > Hi Yee-Kang > > I'm looking at applying this patch but having a little trouble. It seems > that the patch file includes duplicate entries which results with undesirable > results at my end (some files are twice as long as they should be). For > example, if you open the patch you see that "requestcontext/pom.xml" appears > twice. Can you try regenerating to remove these duplications? > > This seems to be a feature for the patches for 2231, 2232, 2233 also. > > > 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: Simon Laws > > Attachments: RequestContextJIRA2230.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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can @ConversationID apply on private variable?
The Specification is inconsistent since: 504 If a *protected* or *public* field or setter method is annotated with @ConversationID, then the conversation 505 ID for the conversation is injected onto the field ... My guess is that the example has a typo and should actually be: 1710 @ConversationID 1711 protected String ConversationID; --Kevin On Fri, Apr 11, 2008 at 10:01 AM, Gilbert Kwan <[EMAIL PROTECTED]> wrote: > In the spec of "Java Common Annotations and APIs" > > (http://www.osoa.org/download/attachments/35/SCA_JavaAnnotationsAndAPIs_V100.pdf?version=1), > line 1710-1711 says > > 1710 @ConversationID > 1711 private String ConversationID; > > I tried and got following warning: > Apr 11, 2008 11:50:37 AM > > org.apache.tuscany.sca.implementation.java.introspect.impl.JavaIntrospectionHelper > checkInvalidAnnotations > WARNING: Invalid annotation @org.osoa.sca.annotations.ConversationID() > is found on private java.lang.String > > org.apache.tuscany.sca.vtest.javaapi.annotations.scope.impl.IServiceImpl.conversationId > > Is it a spec or implementation error? > > Thanks > Gilbert > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - 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]
Re: vtest?
Hi Ant, Sorry for causing any confusion. Let me know if you'd like any more explanation. I'll be checking mail sporadically the next several days. --Kevin On Mon, Apr 7, 2008 at 3:04 AM, ant elder <[EMAIL PROTECTED]> wrote: > Answering my own email...I guess its this thread which just doesn't > explicitly refer to "vtest" so it was hard to find the link by searching - > http://apache.markmail.org/message/tmdncjr7vcnmvh3b > > ...ant > > > On Mon, Apr 7, 2008 at 9:12 AM, ant elder <[EMAIL PROTECTED]> wrote: > > > I see we've now a new vtest top-level folder in the trunk and various dev > > happening there. Looking back in the mailing list I cant find any discussion > > on adding that or what its about, am i just missing the emails or whats > > going on there? > > > >...ant > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Updated: (TUSCANY-2195) Test cases for ComponentContext API
Hi Yee-Kang, It would be much easier for me if you could provide your updates as a patch file. Let me know if you need guidance on creating such a file. Instructions can also be found in the developers guide. Thanks, --Kevin On Fri, Apr 4, 2008 at 2:39 PM, Yee-Kang Chang (JIRA) wrote: > > > [ > https://issues.apache.org/jira/browse/TUSCANY-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Yee-Kang Chang updated TUSCANY-2195: > > > Attachment: ComponentContext20080404.zip > > Hi Kevin, > > Here's an update to the ComponentContext test cases. > > Thank you. > > > 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 > > Attachments: ComponentContext.zip, ComponentContext20080404.zip > > > > > > 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] > > - 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]
Next week
Hi All, I will be out next week and would really appreciate it if any committers with extra time on their hands (right!) could apply patches arriving for the vtest buckets. Thanks, --Kevin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ComponentContext.createSelfReference() with and without serviceName
I meant to say: ... an exception is expected if you use the first version of the createSelfReference API to create a ServiceReference to a component offering multiple services. -- Kevin On Fri, Apr 4, 2008 at 10:24 AM, Kevin Williams <[EMAIL PROTECTED]> wrote: > Hi Yee-Kang, > > Further down in the specification is: > >435 The second variant, which takes an additional serviceName > parameter, *must* be used if the component >436 implements multiple services. > > So, an exception is expected if you employ the first version of the > createSelfReference API. > > --Kevin > > > > On Fri, Apr 4, 2008 at 9:42 AM, Yee-Kang Chang <[EMAIL PROTECTED]> wrote: > > > > Hi Everyone, > > > > V1 of the Java Annotations & APIs Spec described these two methods as > > follows: > > > > createSelfReference(Class businessInterface) ? Returns a > > ServiceReference that can be used to invoke this component over the > > designated service. > > createSelfReference(Class businessInterface, String serviceName) ? > > Returns a ServiceReference that can be used to invoke this component over > > the designated service. Service name explicitly declares the service name > > to invoke. > > > > Tuscany's JavaDoc described them as such: > > > > createSelfReference(java.lang.Class businessInterface) Returns a > > ServiceReference that can be used to invoke this component over the > > default service. > > createSelfReference(java.lang.Class businessInterface, java.lang.String > > serviceName)Returns a ServiceReference that can be used to invoke this > > component over the designated service. > > > > The behaviour I observed was that createSelfReference(java.lang.Class > > businessInterface) would return an Exception when I invoked it from a > > component with more than one services defined. > > > > Can someone please confirm that this is the expected behaviour and that > > createSelfReference(java.lang.Class businessInterface) is meant for > > component with one service while createSelfReference(java.lang.Class > > businessInterface, java.lang.String serviceName) is meant for component > > with multiple services? And so, the "default service" mentioned in > > Tuscany's JavaDoc is a typo? > > > > Thank you! > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ComponentContext.createSelfReference() with and without serviceName
Hi Yee-Kang, Further down in the specification is: 435 The second variant, which takes an additional serviceName parameter, *must* be used if the component 436 implements multiple services. So, an exception is expected if you employ the first version of the createSelfReference API. --Kevin On Fri, Apr 4, 2008 at 9:42 AM, Yee-Kang Chang <[EMAIL PROTECTED]> wrote: > Hi Everyone, > > V1 of the Java Annotations & APIs Spec described these two methods as > follows: > > createSelfReference(Class businessInterface) ? Returns a > ServiceReference that can be used to invoke this component over the > designated service. > createSelfReference(Class businessInterface, String serviceName) ? > Returns a ServiceReference that can be used to invoke this component over > the designated service. Service name explicitly declares the service name > to invoke. > > Tuscany's JavaDoc described them as such: > > createSelfReference(java.lang.Class businessInterface) Returns a > ServiceReference that can be used to invoke this component over the > default service. > createSelfReference(java.lang.Class businessInterface, java.lang.String > serviceName)Returns a ServiceReference that can be used to invoke this > component over the designated service. > > The behaviour I observed was that createSelfReference(java.lang.Class > businessInterface) would return an Exception when I invoked it from a > component with more than one services defined. > > Can someone please confirm that this is the expected behaviour and that > createSelfReference(java.lang.Class businessInterface) is meant for > component with one service while createSelfReference(java.lang.Class > businessInterface, java.lang.String serviceName) is meant for component > with multiple services? And so, the "default service" mentioned in > Tuscany's JavaDoc is a typo? > > Thank you! > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Verification Testing
Hi Yee-Kang, I just created TUSCANY-2195 to accept and track testing for ComponentContext. You can attach your contribution there. Thanks, --Kevin On Thu, Apr 3, 2008 at 3:55 PM, Yee-Kang Chang <[EMAIL PROTECTED]> wrote: > I've some test cases for ComponentContext that I would like to contribute. > Can someone please help me out with them? Thank you. > > > > > Yee-Kang Chang/Toronto/[EMAIL PROTECTED] > 04/03/2008 12:01 PM > > Please respond to > tuscany-dev@ws.apache.org > > > To > tuscany-dev@ws.apache.org > cc > > Subject > Re: Verification Testing > > > > > > > > Hi Kevin, I would like to contribute to this effort. Thanks! > > "Kevin Williams" <[EMAIL PROTECTED]> > 03/19/2008 01:40 PM > Please respond to > tuscany-dev@ws.apache.org > > To > tuscany-dev@ws.apache.org > cc > [EMAIL PROTECTED] > Subject > Verification Testing > > I am thinking of adding a new test bucket specifically for > verification testing against the specification set. I believe it > would add value to the project and may also be a place where > developers new to Tuscany might contribute. Does this sound like a > reasonable idea? > Thanks, > --Kevin > > - 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]
[vtest] getCompositeContext API for non-SCA clients
The current JUnit tests (iTest and vTest) make use of the non-standard SCADomain.getService API to get a handle to an SCA service. Are there any plans to provide an API to get a ComponentContext as outlined by the SCA Java Annotations and APIs specification? I would like to stick to stick to specified APIs as much as possible in vTest. 1.4.2.1. ComponentContext Non-SCA client code can use the ComponentContext API to perform operations against a component in an SCA domain. How client code obtains a reference to a ComponentContext is runtime specific. The following example demonstrates the use of the component Context API by non-SCA code: ComponentContext context = // obtained through host environment-specific means HelloService helloService = context.getService(HelloService.class,"HelloService"); Thanks. -- Kevin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fw: [jira] Created: (TUSCANY-2165) Java runtime should inject service references to field with common name in absence of @Reference
Hi Gilbert, Thanks! I just opened Tuscany-2188 to track @Service testing. You can post your code there and I will take a look. -- Kevin On Wed, Apr 2, 2008 at 11:13 AM, Gilbert Kwan <[EMAIL PROTECTED]> wrote: > I would like to contribute a similar test about @Service for the section of > 1.2.1 and 1.8.17 of "SCA Java Common Annotations and APIs V1.00 " > specification. > Regards > Gilbert Kwan > > > > On Wed, Apr 2, 2008 at 1:11 PM, Gilbert Kwan <[EMAIL PROTECTED]> wrote: > > > > > > > > > Gilbert Kwan > > > > - Forwarded by Gilbert Kwan/Toronto/IBM on 04/02/2008 01:11 PM - > > > > "Kevin Williams > > (JIRA)" > > <[EMAIL PROTECTED] To > > pache.org>tuscany-dev@ws.apache.org > >cc > > 03/29/2008 06:03 > > PMSubject > > [jira] Created: (TUSCANY-2165) Java > > runtime should inject service > > Please respond to references to field with common > > [EMAIL PROTECTED] name in absence of @Reference > > ache.org > > > > > > > > > > > > > > > > > > > > > > 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] > > > > > > > - 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]
[vTest] Wiki content
I would like to add page to our wiki devoted to vtest development. I see this as a place where we can provide a mapping from the specification set to specific test buckets and also as a place to track progress. Any thoughts? -- Kevin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[vtest] new Jira component
I have added a new jira component named "Java SCA Verification Tests" and I will start opening issues for specific areas of the Java Annotations and APIs specification that require testing. Thanks, --Kevin - 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]
Re: Verification Testing
These are good points. I'll think about making line numbers work. Thanks. - Kevin On Fri, Mar 28, 2008 at 10:52 AM, Luciano Resende <[EMAIL PROTECTED]> wrote: > I'd say that publishing a modified (in this case annotated) version of > the specification might have licensing issues. Also, as there is no > "compliance test" or a clear "compliance definition" on the spec, your > annotations around this area might be controversial. > > > > > On Fri, Mar 28, 2008 at 9:12 AM, Kevin Williams <[EMAIL PROTECTED]> wrote: > > I think that named annotations would be more clear since there is not > > a direct mapping from line number to compliance point. A compliance > > point may cover n lines or a single line may have n compliance points. > > > > > > > > On Fri, Mar 28, 2008 at 9:47 AM, Simon Nash <[EMAIL PROTECTED]> wrote: > > > Kevin Williams wrote: > > > > I'd like to add an annotated version of the SCA Java Common > > > > Annotations and APIs specification somewhere in the project so that I > > > > can reference individual functional requirements from the tests. > Does > > > > it make sense to add this as an attachment to the Java SCA > > > > Documentation wiki page? > > > > > > > If the references are from the tests to the spec, it should be > > > possible to use spec line numbers and not modify the spec. > > > Is there some problem with this? > > > > > >Simon > > > > > > > > > > > > > Thanks, > > > > > > > > --Kevin > > > > > > > > On Thu, Mar 20, 2008 at 11:22 AM, Kevin Williams <[EMAIL PROTECTED]> > wrote: > > > >> I would like to tie individual tests in this new suite to specific > > > >> functional requirements from the specifications. The best way to > do > > > >> this may be to reference named requirements from annotated > versions of > > > >> the specs. > > > >> > > > >> Would it make sense to store these annotated versions somewhere in > the project? > > > >> > > > >> Thanks, > > > >> > > > >> --Kevin > > > >> > > > >> > > > >> > > > >> On Thu, Mar 20, 2008 at 3:21 AM, Vamsavardhana Reddy > > > >> <[EMAIL PROTECTED]> wrote: > > > >> > +1 > > > >> > > > > >> > ++Vamsi > > > >> > > > > >> > On Wed, Mar 19, 2008 at 11:10 PM, Kevin Williams <[EMAIL > PROTECTED]> > > > >> > wrote: > > > >> > > > > >> > > > > >> > > > > >> > > I am thinking of adding a new test bucket specifically for > > > >> > > verification testing against the specification set. I > believe it > > > >> > > would add value to the project and may also be a place where > > > >> > > developers new to Tuscany might contribute. Does this sound > like a > > > >> > > reasonable idea? > > > >> > > Thanks, > > > >> > > --Kevin > > > >> > > > > > >> > > > > >> > > > > >> > > > - > > > >> > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >> > > For additional commands, e-mail: [EMAIL PROTECTED] > > > >> > > > > > >> > > > > > >> > > > > >> > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > Luciano Resende > Apache Tuscany Committer > http://people.apache.org/~lresende > http://lresende.blogspot.com/ > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Verification Testing
I think that named annotations would be more clear since there is not a direct mapping from line number to compliance point. A compliance point may cover n lines or a single line may have n compliance points. On Fri, Mar 28, 2008 at 9:47 AM, Simon Nash <[EMAIL PROTECTED]> wrote: > Kevin Williams wrote: > > I'd like to add an annotated version of the SCA Java Common > > Annotations and APIs specification somewhere in the project so that I > > can reference individual functional requirements from the tests. Does > > it make sense to add this as an attachment to the Java SCA > > Documentation wiki page? > > > If the references are from the tests to the spec, it should be > possible to use spec line numbers and not modify the spec. > Is there some problem with this? > >Simon > > > > > Thanks, > > > > --Kevin > > > > On Thu, Mar 20, 2008 at 11:22 AM, Kevin Williams <[EMAIL PROTECTED]> wrote: > >> I would like to tie individual tests in this new suite to specific > >> functional requirements from the specifications. The best way to do > >> this may be to reference named requirements from annotated versions of > >> the specs. > >> > >> Would it make sense to store these annotated versions somewhere in the > project? > >> > >> Thanks, > >> > >> --Kevin > >> > >> > >> > >> On Thu, Mar 20, 2008 at 3:21 AM, Vamsavardhana Reddy > >> <[EMAIL PROTECTED]> wrote: > >> > +1 > >> > > >> > ++Vamsi > >> > > >> > On Wed, Mar 19, 2008 at 11:10 PM, Kevin Williams <[EMAIL PROTECTED]> > >> > wrote: > >> > > >> > > >> > > >> > > I am thinking of adding a new test bucket specifically for > >> > > verification testing against the specification set. I believe it > >> > > would add value to the project and may also be a place where > >> > > developers new to Tuscany might contribute. Does this sound like a > >> > > reasonable idea? > >> > > Thanks, > >> > > --Kevin > >> > > > >> > > >> > > >> > > - > >> > > To unsubscribe, e-mail: [EMAIL PROTECTED] > >> > > For additional commands, e-mail: [EMAIL PROTECTED] > >> > > > >> > > > >> > > >> > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - 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]
