Problems in Resolving Artifacts via Imports/Exports between Multiple
Contributions
----------------------------------------------------------------------------------
Key: TUSCANY-3012
URL: https://issues.apache.org/jira/browse/TUSCANY-3012
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-2.0
Reporter: Mike Edwards
Assignee: Mike Edwards
Priority: Minor
Fix For: Java-SCA-2.0
The OASIS SCA Assembly tests which deal with Contributions and <import/> and
<export/> statements in sca-contribution.xml files revealed problems in the way
that artifact resolution is handled within Tuscany.
When using more than 2 contributions, with imports and exports taking place
between 3 or more contributions, exceptions can occur where resolving an
artifact in contribution A follows an import to an export in contribution B.
It can be that contribution B has not yet been resolved - and as a result the
export class in B is not initialized for resolving the incoming resolve request
from the export in A.
The current code attempts to deal with this by ordering the resolution of the
contributions. However, there are no clear criteria for the ordering,
especially if different kinds of artifacts (eg composites, Java classes) are
being imported from multiple locations and are resolved to different locations.
As a result, the code is in practice unable to derive a resolution order that
will work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
