The latest OASIS SCA Assembly Spec has the following:
3509 When a contribution contains a reference to an artifact from a
namespace that is declared in an import
3510 statement of the contribution, if the SCA artifact resolution mechanism
is used to resolve the artifact, the
3511 SCA runtime MUST resolve artifacts in the following order:
3512 1. from the locations identified by the import statement(s) for the
namespace. Locations MUST NOT
3513 be searched recursively in order to locate artifacts (i.e. only a
one-level search is performed).
3514 2. from the contents of the contribution itself. [ASM12023]
So it should be import first and local second. This is also the order that
OSGi uses to resolve the classes.
--------------------------------------------------
From: "Scott Kurz" <scottk...@gmail.com>
Sent: Wednesday, April 22, 2009 12:14 PM
To: <dev@tuscany.apache.org>
Subject: Re: [DISCUSS] Use of Existing (non-SCA) Mechanisms for Resolving
Artifacts
Ram,
Thanks for the updated summary.
I have a couple of questions, if you don't mind.
First, this is probably an obvious question, but by the "SCA
resolution mechanism" you mean:
1. first look in the current contribution
and if not found
2. then look for SCA contribution import/exports.
Second, the behavior you described makes sense to me, but we do agree
it is not what the Assembly spec says, right? I am not trying to
push on spec compliance at the moment, just getting clear since we'd
been discussing the spec statement in the past.
Thanks, Scott
