Hi,
With SCARuntimeActivator, we use the contribution service to discover all
the composites in the "default contribution" which is the jar/folder that
contains the composite path from the start() method. If there is
META-INF/contribution-metadata.xml that lists the deployable composites,
then only the deployables will be actiavated. Othwerwise, all the composites
will be treated as deployables and added to the SCA domain. When a composite
is activated, it's included in the SCA domain composite and top-level
components cannot have duplicate names.
The composite passed to the start() method is really a workaround to
discover the root of the default contribution. Maybe we should use it as the
deployable in case that no META-INF/contribution-metadata.xml is present.
Thanks,
Raymond
----- Original Message -----
From: "ant elder" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, May 04, 2007 8:17 AM
Subject: SCARuntimeActivator and multiple .composite files
I've a problem using SCARuntimeActivator with implementation-script tests
as
it fails saying there are components with duplicate names. This looks like
its because there are multiple .composite files for all the various
testcases which do use the same component names and they're all getting
found and used even though the SCARuntimeActivator start method takes a
composite name. How should this work? Should all the .composite files get
used (so why does SCARuntimeActivator.start need a composite name?)
Should
it be possible to do unit tests like the script impl does with lots of
individual .composite files?
See
https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/implementation-script/src/test/resources/org/apache/tuscany/sca/implementation/script/itests/
...ant
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
