Simon Laws wrote:
I just tried this with the JMS test, i.e. added a second composite,
and it
does feel a little odd. In the case where there is no
sca-contribution.xmlthe logc seems to look for the directory that
holds the composite file you
specify and load all the composites there rather that just the one you
ask
for. Is that right?
Simon
Simon,
If I remember correctly here's our strategy for determining deployable
composites in a contribution:
- the composites passed to SCADomain.newInstance() are considered deployable
- if there's a META-INF/sca-contirbution.xml, we should get a list of
deployables from it
- if there's a META-INF/sca-deployables directory, we should add the
composites in that directory to the list of deployables
- add the deployables to domain
Other composites are either:
1. referenced by <include>
2. referenced by <implementation.composite>
3. not referenced
We can defer the processing of composites under case (3) until:
a. an administrator references them in a deployment composite
(deployment composite as described in the spec)
b. an other SCA contribution references the composite (through an
import/export and use case 1. or 2. described above)
As I said previously in that thread, I've already started to look at how
to defer the loading of some of these resources.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
