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
  • Build Your SCA Light Distribution
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

Version 1 Next »

Unable to render {include} The included page could not be found.

(warning) This page is under construction.

What this is about

This page can be used by those who would like to pick and choose pieces of Tuscany and embed it with their software or create smaller distributions to use. It outlines dependencies and identifies the minimum set of modules required to use Tuscany.

Current Tuscany Packaging State

As of release 1.3 Tuscany binaries are distributed via one distribution that includes everything. Based on user feedback, choice of a smaller distribution packages is desireable. Tuscany community is in the process of addressing this requirement. Please see discussions on the mailing list and contribute if interested.

How to build your own distribution

Let's use the term "feature" to refer to a package. This is also used in Eclipse and many people are familiar with it.

A Tuscany user has defined a set of features applicable to his application at this location. Althought these features address this user's requirements, there might be variations of packaging that other users may need(we would like to hear your opinion). We realize that there will always be a need for smaller features or a combination of features. For that reason, this page is created to help you understand dependencies and be able to create your own distribution if needed.

For the sake of this conversation, let's assume that the minimum bar is a distribution that allows you to do the following
1. Build SCA applications
2. Access external services through webservice
3. Use web20

Let's use the existing features in the source tree as a starting point to see if the modules bundled are sufficient to define the dependency of modules required to do the above 3 taskes.

  • core feature - pom.xml
    This package includes support for building applications based on Java components and also exposes SPIs for extending Tuscany SCA to include extensions such as binding types, implementation types, policies.
    This could be the minimum required to use Tuscany.
    • Included in this feature:
      1. Core runtime includes OSGI support
      2. Launchers
      2a) j2Se
      2b) equinox
      2c) Webapp
      3. Bindings:
      2a) SCA default binding
      2b) corba (as a light weight binding that you can use with the core distro
      4. Data Bindings: Jaxb
      5. Interfaces
      4a) Java
      4b) Wsdl
      Is this sufficient?
  • webservice feature - pom.xml
    This package provides support for webservices binding based on Axis2.
    • Included in this feature:
      1. Core Runtime: Core feature
      2. support for webservices
      In addition to what is included in core feature:
      3. Bindings; ws, ws-axi2, ws-wsdlgen, ws-xml
      4. Databindings: Jaxb-axiom, SDO, SDO-axiom
      Is this sufficient?
  • web20 feature - pom.xml
    This package enables you to use web20 with Tuscany.
    • Included in this feature:
      1. Core Runtime: Core feature
      2. Support for resources and widgets
      In addition to what is included in core feature:
      3. Bindings; Atom (via Abdrea), Jason, RSS (via Rome), HTTP,
      4. Databindings: JSON

Is this sufficient?

How to build my own distribution?

(I am really struggling with how to identify dependencies the easiest way so that we don't have to keep a static table)

Understanding dependencies

To understand module dependencies, you can start with a particular feature and run one of the following commands.

go to the feature directory and issue the command:

mvn:site 

This will create a file called dependencies.html that shows dependencies amongst modules that create this feature.

or for the text version of the dependencies you can use the following command

 mvn dependency:tree 
  • No labels