1. SCA Artifact Loading - OSGI SCA needs to define resource loading for our artifacts 1.Imports first and then private resources. 2.Maintaining loader context.

2. SCA Artifact Loading – implementation.composite Composite – having the right artifact loader Bundle ABundle B export Import B Composite A Composite B bundle A artifact loader bundle B artifact loader impl -composite knows its artifact loader -we also need this for bpel, wsdl, xsd, …

3. SCA Artifact Loading – namespace import/export Loading ns:name identified artifacts, avoid location attributes Bundle ABundle B export Import ns2 bundle A artifact loader bundle B artifact loader Composite A ns1:name12 ns2:name21 ns1 … name11 name12 ns2 … name21 name22 A contribution knows its private and public namespaces and the artifacts that provide them; exported ns stated in contribution export ns1 and ns2 are used as shorthand for namespace names.

4. SCA Artifact Loading – SCA include Remove support for cross contribution sca:include, rather than solve the cross contribution artifact resolution problems. Inclusion MUST be resolved with a contribution.