You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <tu...@ws.apache.org> on 2007/09/20 16:10:31 UTC
[jira] Commented: (TUSCANY-1637) Rationalize the SCA Domain
implementations
[ https://issues.apache.org/jira/browse/TUSCANY-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529116 ]
Simon Laws commented on TUSCANY-1637:
-------------------------------------
The interface changes didn't make it into 1.0. The distributed support is now split between node-* and domain-* modules and this is fronted by an SCADomain like interface in the domain-api module. We need to discuss on the list about where to take SCADomain.
> Rationalize the SCA Domain implementations
> ------------------------------------------
>
> Key: TUSCANY-1637
> URL: https://issues.apache.org/jira/browse/TUSCANY-1637
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Core Runtime, Java SCA Embedded Runtime
> Affects Versions: Java-SCA-0.99
> Reporter: Simon Laws
> Assignee: Simon Laws
> Fix For: Java-SCA-Next
>
>
> We now have a number of domain implementations in Tuscany Java SCA including
> - The SCADomain interface
> - DefaultSCADomain
> - EmbeddedSCADomain
> - HotUpdatableSCADomain
> - DistributedDomain/Node
> - distribution webapp?
> We should try to boil this down to the minimum number of APIs that are required.
> A thread on the ML has been started on this subject
--
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