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 t

[jira] Created: (TUSCANY-2390) Default property value in Component Type Fiel not used to initialize property

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

Re: [jira] Commented: (TUSCANY-2383) Cannot define component property with Component Type File

USCANY-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 componentT

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 b

[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 w

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,

[jira] Created: (TUSCANY-2383) Cannot define component property with Component Type File

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

[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 w

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: tus

[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 referen

[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

[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 ServiceAnnotationTestC

[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

[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 ServiceAnnotationTestC

[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

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 >> >> --

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 feed

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 g

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 docum

[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 docum

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 S

[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 resolutio

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()

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

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. >> >

[jira] Created: (TUSCANY-2311) Second equivalently typed callback field not injected

: 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

Re: [jira] Commented: (TUSCANY-2306) Client callback state preserved through stateless callback

: 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

[jira] Created: (TUSCANY-2306) Client callback state preserved through stateless callback

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 reques

[jira] Created: (TUSCANY-2299) Client-set callback id not preserved on stateless callback

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

[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

[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

[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

[jira] Created: (TUSCANY-2291) Runtime does not detect illegal mix of local and remoteable on bidirectional interface

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

[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

[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 fi

[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-pub

[jira] Created: (TUSCANY-2283) Conversation should end due to non-business exception

: 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

[jira] Created: (TUSCANY-2282) Poor warning issued when annotating private field with @Callback

: 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

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 contri

[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

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

[jira] Created: (TUSCANY-2276) Conversation not started on reference injection

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 servi

[jira] Created: (TUSCANY-2274) @Scope vTest failing intermittently

Versions: Java-SCA-Next Reporter: Kevin Williams The atScope1 vTest fails intermittently like this: --- T E S T S --- Running

Re: [vtest] getCompositeContext API for non-SCA clients

t 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

Re: [vTest] Test design for ConversationAttributes.SinglePrincipal

ny.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 Willia

[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 conv

[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'

[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'

[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'

[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'

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? > > --

[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 vt

[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 vt

[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 ComponentContex

[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/As

[jira] Created: (TUSCANY-2247) vtest content for Java API spec - Conversation/Async

: 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

[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 ServiceReferenc

[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'

[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 -

[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 A

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 TUSCA

[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 A

[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 A

[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

[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.

[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 ServiceRefere

[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

[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 CallableRefere

[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

[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

[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

[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

[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

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

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 @Co

[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 @Sc

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 >

Re: [jira] Updated: (TUSCANY-2195) Test cases for ComponentContext API

: 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 > > Attachment

[jira] Created: (TUSCANY-2199) Tests for @Reference annotation

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

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 PROTECTE

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, > >

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. --Kevi

Re: Verification Testing

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 > >

[jira] Created: (TUSCANY-2195) Test cases for ComponentContext API

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

[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 @Serv

[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

[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

[jira] Created: (TUSCANY-2191) A @Service annotation with no attributes causes exception

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

[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

[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 spe

Re: Fw: [jira] Created: (TUSCANY-2165) Java runtime should inject service references to field with common name in absence of @Reference

> > > > - Forwarded by Gilbert Kwan/Toronto/IBM on 04/02/2008 01:11 PM - > > > > "Kevin Williams > > (JIRA)" > > <[EMAIL PROTECTED] To > >

[jira] Created: (TUSCANY-2188) New tests for Java @Service annotaion

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

[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 -

[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

[jira] Created: (TUSCANY-2165) Java runtime should inject service references to field with common name in absence of @Reference

/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,

Re: Verification Testing

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: >

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

[jira] Created: (TUSCANY-2145) SCADomain.getService () should throw exception when bogus component name is passed

: 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

  1   2   3   4   5   6   >