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

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

[jira] Updated: (TUSCANY-2246) Update DefaultContextFactoryExtensionPoint to use ServiceDiscovery

[ https://issues.apache.org/jira/browse/TUSCANY-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Dritschler updated TUSCANY-2246: - Attachment: tuscany-2246.patch > Update DefaultContextFactoryExtensionPoint to use Serv

Re: Mirror of release artifacts

I have updated the latest Java SCA and SDO download pages to use the mirrors. On Wed, Apr 16, 2008 at 9:18 AM, Luciano Resende <[EMAIL PROTECTED]> wrote: > On Wed, Apr 16, 2008 at 9:15 AM, Robert Burrell Donkin > <[EMAIL PROTECTED]> wrote: > > On Wed, Apr 16, 2008 at 4:51 PM, Luciano Resende <[E

[jira] Created: (TUSCANY-2246) Update DefaultContextFactoryExtensionPoint to use ServiceDiscovery

Update DefaultContextFactoryExtensionPoint to use ServiceDiscovery -- Key: TUSCANY-2246 URL: https://issues.apache.org/jira/browse/TUSCANY-2246 Project: Tuscany Issue Type: Impr

Workpool Porting: Adding Component to an existing composite

I'm going to review my JIRA 2099. With this patch i modified composite wire builder and composite configuration adding a wireComponent /unWireComponent and configureComponent. The objective of this work is to give the user the possibility to add dinamically a new component inside a given composite.

[jira] Commented: (TUSCANY-2239) Support for mutually-exclusive intents

[ https://issues.apache.org/jira/browse/TUSCANY-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590785#action_12590785 ] Greg Dritschler commented on TUSCANY-2239: -- I have attached a new patch for Comp

[jira] Updated: (TUSCANY-2239) Support for mutually-exclusive intents

[ https://issues.apache.org/jira/browse/TUSCANY-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Dritschler updated TUSCANY-2239: - Attachment: tuscany-2239-CompositeWireBuilder.patch > Support for mutually-exclusive in

[jira] Updated: (TUSCANY-2239) Support for mutually-exclusive intents

[ https://issues.apache.org/jira/browse/TUSCANY-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Dritschler updated TUSCANY-2239: - Attachment: (was: tuscany-2239-CompositeWireBuilder.patch) > Support for mutually-e

[jira] Updated: (TUSCANY-2239) Support for mutually-exclusive intents

[ https://issues.apache.org/jira/browse/TUSCANY-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Dritschler updated TUSCANY-2239: - Attachment: tuscany-2239-CompositeWireBuilder.patch > Support for mutually-exclusive in

Re: [jira] Created: (TUSCANY-2239) Support for mutually-exclusive intents

The patch validates the final list of intents collected into the binding or implementation does not contain exclusive intents. I suppose you could do validation calls at other levels to better pinpoint the source of the error. Greg On Sat, Apr 19, 2008 at 7:37 AM, Venkata Krishnan <[EMAIL PROTEC