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

« Previous Version 3 Next »

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

(warning) This page will move to the website when it is complete. Please help to complete it. Thanks.

What this is about

As of release 1.3 Tuscany SCA is distributed via one binary 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 mailing list for that discussion. This is not the purpose of this page.

Tuscany users have asked for a write-up that highlights module dependencies. This enables them to build their own distribution which may have a lower or higher granularity than the pre-packaged binary distributions. Purpose of this page is to help users understand how to build their own tuscany SCA light distribution based on module dependency knowledge that is shared here.

Therefore:
This page is not about building Tuscany building binary distributions to distribute
This page is about understanding dependencies so that users can build their own distribution

How to build your own distribution

Let's first understand the different categories of module types in Tuscany. This understanding will help us determine how to put the modules together to have a runnable and useful system.

  • Core type modules- These are modules that enable you to use SCA programming model to create applications
  • Binding type modules - Bindings handle protocols between two services. Tuscany supports many bindings. One or more modules constitute a binding.
  • Component type modules - These are the modules that enable you to use different languages or container models to create SCA components. Tuscany supports different component types. There are a set of modules that support each component type. For example, java, BPEL, Spring, etc. There are specific modules that support a given component type.
  • Policies type modules- There are different policy types. For example security, monitoriing, etc. There are specific modules that support each policy.
  • Databinding type modules - These modules support data types. Tuscany supports many data bindings, including Jaxb, SDO, Axiom, Json/rpc. There are specific modules that support a given data binding.
  • Runtime Type modules- Tuscany supports different runtimes. There are specific modules that support a given runtime.

Now that you understand the different module types, let's identify the module that fall into each category.

Understanding dependencies

<Insert dependencies>
(Struggling with how best to demonstrate this. An idea might be a table of module names that fall into categories. for example under binding we would have various binding names, their modules and description)

Minimum rquired to build and run SCA applications

Sample pom

Examples for including bindings

sample pom for one or two bindings?

Examples for including Web20

sample pom

Core with different runtimes?

  • No labels