Note |
---|
| title:Notification |
---|
| title:Notification |
---|
| Center |
---|
This page is under construction- You are welcome to help and complete it |
|
Background Color |
---|
| A presentation on how to extend Tuscany in Microsoft PowerPoint format |
Extending Tuscany PPT PDF Background Color |
---|
| What is an extension? |
Extension is a module (or a set of modules),when built with Tuscany SCA, can extend it to work with additional bindings, language implementations, programming models or databindings. SCA assembly model is defined such that extensions can be added for new interface types or for new implementation types such as ruby and python, or new binding types such as CXF. However, the definition of extension SPIs is left to the implementor. Tuscany SCA Java provides a simple set of SPIs for implementing extensions. It also defines additional extension points such as data binding, for example support for SDO and JAXB. This guide explains the steps to add each of these extension types. Please help us refine the guide as you go through the steps of adding extensions. Name spaces used by extensionsExtensions sometimes contribute addtional elements or attributes to the SCA XML configuration model. These elements or attributes should be qualified as follows: Background Color |
---|
| How to add a new component implementation? |
Musings on Adding a New Implementation Type by Mike E Background Color |
---|
| How to add a new binding? |
Background Color |
---|
| How to add a new interface binding? |
Background Color |
---|
| How to add a new databinding? |
Background Color |
---|
| How to add a new monitor extension? |
The need for monitor extension came as a requirement, to have a customized exception handling on Tuscany runtime especially when the user input errors are determined while reading, resolving and building phase of the contribution within the Tuscany runtime. Here different users/vendors using Tuscany with their products wanted to ignore some of the user input errors and allow the runtime to proceed further, while the others wanted to stop processing when a error is determined at the end of each phase. Another important need for a monitor extension is to validate the user inputs (via contributions) and report all the issues identified in one go (Example: As how the java compiler does for java code). Understanding message conversion using monitor1) Errors and warnings are logged with the monitor as problems and the processing continues. Exceptions won't be thrown, where ever possible. Processing here covers any processing of user input, i.e. contributions and the artifacts they contain.
|