I found that I needed to make a few small changes to the
ContributionContentProcessor to handle contributions with no
sca-contribution.xml, like existing regular JARs for example.
I've been able to use regular JARs in an SCA domain with the following
changes:
- define DefaultImport/DefaultExport objects (similar to the other kinds
of imports/exports that we already have)
- have ContributionContentProcessor add DefaultImport/DefaultExport to
the Contribution model if no sca-contribution.xml is found in a
contribution.
- process and hook together the DefaultImports/Exports in
ContributionDependencyBuilder
- if found, use the DefaultImports to resolve model in the particular
modelresolvers, like WSDLModelResolver for example.
This seems to work and not break anything, the changes are in
sandbox/sebastien/sca-test2 if people want to take a look (see commit
r663461).
I'll do more testing in trunk with the whole itest and vtest suite
before applying the same changes to trunk.
--
Jean-Sebastien
