[
https://issues.apache.org/jira/browse/TUSCANY-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580387#action_12580387
]
Simon Laws commented on TUSCANY-2099:
-------------------------------------
I'm just checking in the patch associated with TUSCANY-2099 and one of the
changes is to fill some gaps in the CompositeActivator's arsenal of component
activation and deactivation methods. I have previous experience of the existing
CompositeActivator methods for deactivating and reactivating components and
their references when implementing some domain/node features before Christmas.
I found them to be somewhat unreliable and I think the feeling at the time was
that they weren't used very much and that they weren't well maintained.
Can I just check with you the mode of operation of the workpool demo and the
way that it uses these methods to add new worker components. The question on my
mind is is it important that new components are added to the composite to
service new jobs in parallel or is it, instead, a matter of ensuring that
sufficient instances of an existing component are available to service tasks?
Simon
> Porting Workpool-Distributed demo to current.
> ---------------------------------------------
>
> Key: TUSCANY-2099
> URL: https://issues.apache.org/jira/browse/TUSCANY-2099
> Project: Tuscany
> Issue Type: New Feature
> Reporter: Giorgio Zoppi
> Assignee: Simon Laws
> Fix For: Java-SCA-Next
>
> Attachments: firstpatch.diff
>
>
> This is the first patch to adapt workpool demo to current. Still it doens't
> compile.
--
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]
