summaryrefslogtreecommitdiffstats
path: root/tags/site-090106-pre667/site-author/sca-composite.xml
diff options
context:
space:
mode:
Diffstat (limited to 'tags/site-090106-pre667/site-author/sca-composite.xml')
-rw-r--r--tags/site-090106-pre667/site-author/sca-composite.xml24
1 files changed, 0 insertions, 24 deletions
diff --git a/tags/site-090106-pre667/site-author/sca-composite.xml b/tags/site-090106-pre667/site-author/sca-composite.xml
deleted file mode 100644
index a3a5c2b813..0000000000
--- a/tags/site-090106-pre667/site-author/sca-composite.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<document>
- <properties>
- <title>Tuscany</title>
- <bannertitle>Tuscany SCA Composite</bannertitle>
- </properties>
- <body>
- <section name="Composite">
-<p>
-An SCA composite is used to assemble components in logical groupings. It is the basic unit of composition within an SCA System. An SCA Composite contains a set of Components, Services, References and the Wires that interconnect them. Composites are component implementations in higher-level composites in other words
-composites can have components that are implemented by composites.
-</p>
-<p>
-A composite has the following normative characteristics:
-</p>
-<ul>
-<li>It defines a boundary for Component visibility. Components may not be directly referenced outside of the composite that contains them.</li>
-<li>It can be used as a unit of deployment. Composites are used to contribute business services to an SCA system.</li>
-
-</ul>
-
- </section>
- </body>
-</document>