You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tuscany.apache.org by aj...@apache.org on 2006/10/16 17:35:40 UTC
svn commit: r464521 - /incubator/tuscany/cpp/sca/doc/CPPComponents.html
Author: ajborley
Date: Mon Oct 16 08:35:39 2006
New Revision: 464521
URL: http://svn.apache.org/viewvc?view=rev&rev=464521
Log:
Various updates to address the issues in TUSCANY-850
Modified:
incubator/tuscany/cpp/sca/doc/CPPComponents.html
Modified: incubator/tuscany/cpp/sca/doc/CPPComponents.html
URL: http://svn.apache.org/viewvc/incubator/tuscany/cpp/sca/doc/CPPComponents.html?view=diff&rev=464521&r1=464520&r2=464521
==============================================================================
--- incubator/tuscany/cpp/sca/doc/CPPComponents.html (original)
+++ incubator/tuscany/cpp/sca/doc/CPPComponents.html Mon Oct 16 08:35:39 2006
@@ -53,9 +53,8 @@
</DIV>
<DIV CLASS="section">
<H2>Creating and deploying an SCA C++ Component</H2>
-
- <P>Each SCA C++ component needs:
- </P>
+ <P>Each SCA C++ component needs:
+ </P>
<UL>
<LI>A service header file that defines the operations that can be invoked on the
component
@@ -69,13 +68,19 @@
<LI>Proxy and wrapper header and implementation files generated by the Tuscany
C++ SCAGEN tool
</LI>
- <LI>A component definition in a composite file
- </LI>
<LI>A service definition in a .componentType file
</LI>
- <LI>A composite describing the configuration of the composite definition above
+ <LI>An SCDL component definition within an SCDL composite file. Usually this
+ composite file will contain multiple components configured and assembled together.
</LI>
- </UL>
+ </UL>
+ <P>Once these items are in place for each component in your composite, you will need to
+ deploy this composite to your SCA system. In this release we are
+ using the SCA recursive composition model to do this. You simply create another
+ SCDL component definition in a separate composite file that will represent the composite
+ you created above in the SCA system. Follow the steps below to see each of these items
+ being created and used.
+ </P>
<P>In this section we will use the Calculator sample as a worked example.
The Calculator code and files can be found at samples/Calculator and has been
developed further than the details specified below. In the interests of
@@ -210,10 +215,10 @@
produce a .dll or .so library file. The name should match the library name
specified in the sample.calculator.composite file.
</LI>
- <LI>Create the sample.calculator.solution.composite file and define your composite
- component within it. The composite component definition should specify the service
- name used in the componentType file and the composite name used in the
- sample.calculator.composite file. E.g. the Calculator sample.calculator.solution.composite
+ <LI>Create the sample.calculator.solution.composite file and define the Calculator composite
+ as a component within it. This is used to include the Calculator composite in the SCA system
+ and should specify the composite name used in the sample.calculator.composite file.
+ E.g. the Calculator sample.calculator.solution.composite
file contains the following XML:<BR/>
<PRE><composite xmlns="http://www.osoa.org/xmlns/sca/1.0"
name="sample.calculator.solution">
@@ -226,8 +231,6 @@
</LI>
<LI>Deploy the various files into the SCA directory structure, as follows:
<UL>
- <LI><deploy_root>/CompositeName/ServiceHeader.h</LI>
- <LI><deploy_root>/CompositeName/ImplementationHeader.h </LI>
<LI><deploy_root>/CompositeName/CompositeName.composite </LI>
<LI><deploy_root>/CompositeName/Implementation.componentType </LI>
<LI><deploy_root>/CompositeName/Implementation.dll (or .so on Linux) </LI>
@@ -276,6 +279,11 @@
your LD_LIBRARY_PATH on Linux. You will also need to set the TUSCANY_SCACPP_SYSTEM_ROOT
and TUSCANY_SCACPP_DEFAULT_COMPONENT environment variables to the
path to your SCA component directory structure and the default component respectively.
+ TUSCANY_SCACPP_SYSTEM_ROOT is the directory where the SCA runtime will look for any
+ .composite files and TUSCANY_SCACPP_DEFAULT_COMPONENT is the name of the base component
+ to be used by SCA clients or containers when finding services - this component must be
+ an instance of a composite (i.e. contain an <implementation.composite> element).
+ <BR/>
E.g. on Windows run the following commands:
<UL>
<LI>set TUSCANY_SCACPP=C:/tuscany_sca </LI>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-commits-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-commits-help@ws.apache.org