History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: ASSEMBLY-8
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Mike Edwards
Reporter: Martin Chapman
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
OASIS SCA Assembly TC

SCDL artifact resolution underspecified

Created: 08/Oct/07 08:46 AM   Updated: 21/Jan/09 04:23 AM
Component/s: Assembly
Affects Version/s: None
Fix Version/s: None


 Description  « Hide
REPORTER: Henning Blohm (SAP)

http://lists.oasis-open.org/archives/sca-assembly/200710/msg00034.html

Title: NEW ISSUE: SCDL artifact resolution underspecified
TARGET: Assembly specification, section "SCA Artifact Resolution" (1.10.2.1)

DESCRIPTION: Resolution of SCDL artifacts is currently specified only as far as cross-contribution export/import is concerned. As far as QName to SCDL artifact resolution within a contribution is concerned the specification does not say what is the exact scope of such resolution nor how to extend/modify that scope.

Choosing the whole contribution as resolution scope may be prohibitive considering that contributions may be large and distributed (across different execution environments) so that deep traversal of all contribution resources for scdl artifacts may easily introduce a severe performance problem and easily get out of control from a developer perspective.

As an analogy, suppose the group would perceive a contribution format that would encompass java ee applications together with OSGi bundles. Chosing a contribution wide resolution scope would correspond to chosing a contribution wide class loading scheme (which I assume all agree is highly undesirable).

On the other hand, if the resolution scope is not the whole contribution, it is necessary to allow specification of locations within a contribution.

PROPOSAL:

- use sca-contribution / import as a means to implement a namespace -> location mapping also for contribution-local artifacts

- support an scaLocation attribute to be used for namespace -> location mapping from within SCDL artifacts



 All   Comments   Change History      Sort Order:
Scott Vorthmann [30/Sep/08 11:07 AM]


Mike Edwards: Mike E moves to accept Issue8-Proposal-v6-sca-assembly-1.1-spec-Cd01.doc as the resolution of Issue 8 with the following changes:
Mike Edwards: Add after line 3111:
The SCA runtime must raise an error if an artifact cannot be resolved using these mechanism, if present.
Mike Edwards: Add on line 3104:
Note: This form of artifact resolution does not apply to imports of composite files, as described in Section 6.6
Mike Edwards: Replace end of line 3141/3142:
Mike Edwards: "must be searched in lexical order"
Mike Edwards: Replace 2nd sentence lline 3146/3147:
The first location as defined by lexical order is chosen. If no locations are specified no order exists and the one chosen is implementation dependent.
Mike Edwards: Add a diagram of the example after line 3168.
bob: bob seconds
Mike Edwards: NB the PDF of the document is the normative text
bob: at http://www.oasis-open.org/apps/org/workgroup/sca-assembly/email/archives/200809/bin00000.bin
bob: resolution: resolve Assembly-8 with the motion above w/o


Mike Edwards [31/Dec/08 03:52 AM]
Applied in revision:

sca-assembly-1.1-spec-cd01-rev8.doc

30 Dec 2008

Mike Edwards [21/Jan/09 04:23 AM]
CD02