Simon Laws wrote:
This uncovers a slight wrinkle in the way that definitions.xml files are resolved. Some code in SCADefinitionsProcessor.read() was removed that pre-loaded the resolver with the top level artifacts from defintions.xml. A depth first resolve of these artifacts won't work because of the relationships between the artifacts. I've add the code in to the start of the SCADefinitionsProcessor.resolve() method. Simon
Thanks Simon, that's better but still doesn't cover references across definitions.xml.
To cover all cases I think we a policy-aware ModelResolver implementation that indexes policy definitions and can resolve policy sets, intents, maps etc in these definitions.
Basically the same pattern as what we already do for other 'aggregated' definitions like WSDL, XSD etc.
-- Jean-Sebastien
