In Tuscany, we use a Node to represent a composite that depends on more than
one contributions through the import/export. The list of contributions
(URLs) required for a composite are made available to the runtime that hosts
the node.
SCA domain can also function as a repository of installed contributions. The
node can pull in the contributions in advance (that's how Tuscany works
today) or on demand based on the import/export matching.
Thanks,
Raymond
--------------------------------------------------
From: "ant elder" <[email protected]>
Sent: Wednesday, February 10, 2010 1:27 PM
To: <[email protected]>
Subject: Imports and exports in the distributed domain
Has anyone thought much about how imports and exports might work with
the distributed domain? What I'd like to get working is being able to
have a contribution in one runtime exporting some resources and have
other contributions running in other runtimes and JVMs able to import
those resources. Currently the Tuscany code is designed to expect all
the exported resources to be available from contributions in the same
Node as the contribution doing the importing so to support this the
code needs to be updated in similar ways as was done for the
distributed endpoint targets using the distributed registry and some
remote communication mechanisms. I'm playing around with this now but
i'd be interested in anyone else's thoughts about it.
...ant
