Part 4. Exploring the Tuscany runtime

You’ve now learned how to use Tuscany to design, develop, deploy, and run SCA applications. We hope you’ve enjoyed the SCA experience of writing service components and composing them into applications without having to struggle with infrastructure plumbing. How does this plumbing magic happen? Can you extend it? Part 4 will answer these questions for those who are interested in embedding Tuscany in their environment or extending Tuscany to support additional implementation and binding technologies.

Chapter 13, “Tuscany runtime architecture,” will describe key aspects of the Tuscany internals to help you understand the overall architecture of Tuscany. The chapter will walk you though the primary building blocks of Tuscany and explain how they collaborate to load and run composite applications. Details about the extensibility and pluggability of Tuscany are also illustrated so you can become more familiar with how the Tuscany core interacts with Tuscany extensions. With this knowledge, you’ll be able to tailor and/or extend Tuscany to meet your requirements.

If you need to add new implementation or binding types that aren’t supported by Tuscany out of the box, you’ll get all the help you need from chapter 14, “Extending Tuscany.” This chapter covers the design and implementation of SCA implementation and binding types in detail. It gives step-by-step instructions using code snippets from existing sample binding and implementation extensions in Tuscany. For each step, we’ll explain the roles played between your extension and the Tuscany core runtime and provide guidance for the design of your extension.