Module

Description

SPI packages

Usages

Note

assembly

The model for the artifacts defined by the SCA assembly model
and builders for the model

org.apache.tuscany.sca.assembly
org.apache.tuscany.sca.assembly.builder

model interfaces will be used by other modules
builder interfaces will be used to build the models

assembly-xml

Read/resolve/write the assembly models in XML

org.apache.tuscany.sca.assembly.xml

assembly-xsd

XSDs for various SCA models

binding-sca

Runtime provider for binding.sca

The SCABinding model is defined in assembly
Should be renamed as binding-sca-runtime

binding-sca-xml

Read/resolve/write the binding.sca model in XML

contribution

Conttribution-related models
Scan/process/resolve artifacts within the contributions

org.apache.tuscany.sca.contribution
org.apache.tuscany.sca.contribution.processor
org.apache.tuscany.sca.contribution.resolver
org.apache.tuscany.sca.contribution.scanner

Model for the contribution/artifact/import/export
Artifact processor SPIs
Artifact resolver SPIs
Contribution package scanner SPIs

contribution-java

Model for import.java and export.java

org.apache.tuscany.sca.contribution.java

Model interfaces for import.java and export.java

contribution-namespace

Model for import and export (XML namespace)

org.apache.tuscany.sca.contribution.namespace

Model for import and export

contribution-xml

Handle the read/write/resolve of sca-contribution.xml and sca-contribution-generated.xml

core

org.apache.tuscany.sca.core.assembly
org.apache.tuscany.sca.core.context
org.apache.tuscany.sca.core.conversation
org.apache.tuscany.sca.core.factory
org.apache.tuscany.sca.core.invocation
org.apache.tuscany.sca.core.scope
org.apache.tuscany.sca.core.work

core-databinding

The data transformation interceptor

We need to remove the Export-Package for org.apache.tuscany.sca.core.databinding.processor. It's exported as a workaround for a test case in ws-gen.

core-spi

The SPIs between the core and extension modules (binding, implementation and policy providers)

org.apache.tuscany.sca.context
org.apache.tuscany.sca.endpointresolver
org.apache.tuscany.sca.invocation
org.apache.tuscany.sca.management
org.apache.tuscany.sca.provider
org.apache.tuscany.sca.runtime
org.apache.tuscany.sca.work

databinding

Databinding framework and a set of built-in databindings and transformers

org.apache.tuscany.sca.databinding
org.apache.tuscany.sca.databinding.annotation
org.apache.tuscany.sca.databinding.impl
org.apache.tuscany.sca.databinding.javabeans
org.apache.tuscany.sca.databinding.util
org.apache.tuscany.sca.databinding.xml

Turn some of the implementation classes for DataType into a factory pattern
Refactor some of the utilities into common-xml

databinding-jaxb

JAXB databinding

org.apache.tuscany.sca.databinding.jaxb

JAXB is the default databinding to cover POJOs. We need to find a better way to extract the SPI

definitions

Model and utility for the defintions.xml

org.apache.tuscany.sca.definitions
org.apache.tuscany.sca.definitions.util

definitions-xml

Read/write/resolve definitions.xml

endpoint

Default implementation for EndpointResolver and EndpointResolverFactory

Should we merge this module into core?

extensibility

SPIs to discover extensions/extension points

org.apache.tuscany.sca.core
org.apache.tuscany.sca.extensibility

Extension point registry and core extension points
Extensibility SPIs

extensibility-equinox

Equinox-based extensibility implementation

We might have to export a package so that it can be used to set up the service discoverer for the running environment

implementation-java

implementation-java-runtime

implementation-java-xml

implementation-node

implementation-node-runtime

interface

interface-java

interface-java-jaxws

interface-java-xml

monitor

node-api

node-impl

node-launcher

node-launcher-equinox

policy

policy-security

policy-xml

sca-api

workspace

workspace-impl

workspace-xml

xsd