This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • Contribution - Import and Export
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Contribution use case scenarios

  • Two contributions, where C1 defines and exports CompositeA and C2 imports and reference it trough a <implementation.composite>
  • Two contributions, where C1 defines a WSDL contract and export it's namespace, and C2 imports and reference it through a ws-binding.
  • Two contributions, where C1 defines some interfaces and export it's package, and C2 imports and reference these interfaces

Current Assumptions

  • If a Contribution C1 defines and exports artifacts, it MUST be contributed before another contribution can import these artifacts, otherwise resolutions won't work.
  • Resolution is happening first locally, and then on imported contributions.
  • Import locations are being mapped to contribution URIs
  • No labels