You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "ant elder (JIRA)" <tu...@ws.apache.org> on 2007/08/21 10:33:30 UTC
[jira] Closed: (TUSCANY-1554) Support alternate WorkScheduler
implementations
[ https://issues.apache.org/jira/browse/TUSCANY-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ant elder closed TUSCANY-1554.
------------------------------
Resolution: Fixed
Applied, thanks for the patch!
> Support alternate WorkScheduler implementations
> -----------------------------------------------
>
> Key: TUSCANY-1554
> URL: https://issues.apache.org/jira/browse/TUSCANY-1554
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-0.90
> Reporter: Greg Dritschler
> Assignee: ant elder
> Priority: Minor
> Attachments: Tuscany-1554.patch
>
>
> A patch is submitted that allows Tuscany's implementation of the WorkScheduler SPI, Jsr237WorkScheduler, to be plug-replaced by another implementation. The patch uses the mechanism created in revision 564364 which allows the implementations of registry objects to be created dynamically based on a metadata file.
> In order to simplify things, I took the position that the WorkManager is now a private implementation detail of the WorkScheduler. This avoids the need for the dynamic registry object creation mechanism to support a specialized WorkScheduler constructor. The only use of the WorkManager outside the WorkScheduler was a destroy() call in ReallySmallRuntime. I moved the destroy() method into the WorkScheduler interface.
--
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org