Artifact resolution mechanism - ignore local definition for imported definition
-------------------------------------------------------------------------------
Key: TUSCANY-3079
URL: https://issues.apache.org/jira/browse/TUSCANY-3079
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-2.0-M3
Reporter: Ramkumar Ramalingam
Assignee: Ramkumar Ramalingam
Fix For: Java-SCA-2.0-M3
One important recommendations from the OASIS specs for artifact resolution
mechanism is that....
3458 When a contribution contains a reference to an artifact from a namespace
that is declared in an import
3459 statement of the contribution, if the SCA artifact resolution mechanism is
used to resolve the artifact, the
3460 SCA runtime MUST resolve artifacts in the following order:
3461 1. from the locations identified by the import statement(s) for the
namespace. Locations MUST NOT
3462 be searched recursively in order to locate artifacts (i.e. only a
one-level search is performed).
3463 2. from the contents of the contribution itself. [ASM12023]
3484 The SCA runtime MUST ignore local definitions of an artifact if the
artifact is found through
3485 resolving an import statement. [ASM12024]
Currently, we seem to be doing the opposite by ignoring the imported artifacts
if the local definition of the artifact is found.
So, I will be modifying the ModelResolvers namely WSDLModelResolver,
XSDModelResolver and BPELModelResolver to reflect
what is recommended in OASIS specs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
