avalon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mcconn...@apache.org
Subject cvs commit: avalon-sandbox/merlin/merlin-smp/xdocs/starting/advanced profiles.xml selectors.xml
Date Tue, 08 Apr 2003 11:51:00 GMT
mcconnell    2003/04/08 04:51:00

  Modified:    merlin/merlin-smp/xdocs/starting/advanced profiles.xml
                        selectors.xml
  Log:
  Documentation updating.
  
  Revision  Changes    Path
  1.3       +8 -29     avalon-sandbox/merlin/merlin-smp/xdocs/starting/advanced/profiles.xml
  
  Index: profiles.xml
  ===================================================================
  RCS file: /home/cvs/avalon-sandbox/merlin/merlin-smp/xdocs/starting/advanced/profiles.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- profiles.xml	5 Apr 2003 11:54:27 -0000	1.2
  +++ profiles.xml	8 Apr 2003 11:51:00 -0000	1.3
  @@ -11,30 +11,18 @@
       <section name="Advanced Features">
         <subsection name="Packaged Deployment Profiles">
           <p>
  -          Central to the Merlin component management model is the notion
  -          deployment profiles. A profile is a prefined deployment template. 
  -          It enables Merlin to establish a component type and associated
  -          context, parameterization and/or configuration information as a 
  -          candidate scenario when building a connected set of commponents.
  +Central to the Merlin component management model is the notion deployment profiles. A profile
is a predefined deployment template. It enables Merlin to establish a component type and associated
context, parameterisation and/or configuration information as a candidate scenario when building
a connected set of components.
           </p>
           <p>
  -          Component deployment profiles are co-located with the component
  -          implementation class under a .xprofile resource.
  +Component deployment profiles are co-located with the component implementation class under
a .xprofile resource.
           </p>
         </subsection>
         <subsection name="Creating a Profile">
           <p>
  -          This tutorial extends the interfaces, classes and meta info
  -          declared in the <a href="../hello/dependencies.html">dependencies tutorial</a>

  -          by adding a configurable seed value to the RandomGenerator component. Without
  -          the benefit of a profile, users would be forced to declare a configuration 
  -          under the block.xml directive. By providing one or more profiles, we enable
  -          Merlin to automatically select a deployment scenario candidate and use this
  -          during the assembly phase. 
  +This tutorial extends the interfaces, classes and meta info declared in the <a href="../hello/dependencies.html">dependencies
tutorial</a> by adding a configurable seed value to the RandomGenerator component. Without
the benefit of a profile, users would be forced to declare a configuration under the block.xml
directive. By providing one or more profiles, we enable Merlin to automatically select a deployment
scenario candidate and use this during the assembly phase. 
           </p>
           <p>
  -          The RandomGeneratorProvider source and the corresponding profile directive
  -          is presented below.
  +The RandomGeneratorProvider source and the corresponding profile directive are presented
below.
           </p>
           <p><i>RandomGeneratorProvider.java</i></p>
   <source>
  @@ -84,11 +72,7 @@
   }
   </source>
           <p>
  -          The RandomGeneratorProvider.xprofile contains the defintion of multiple tagged
  -          deployment scenarios.  During assembly Merlin will attempt to locate an explicit
  -          deployment profile (a compoennt declaration in the block.xml).  In no explicit
  -          profile is available Merlin will select a packaged profile based on the xprofile
  -          declarations, otherwise Merlin will attempt to construct an implict profile.
  +The RandomGeneratorProvider.xprofile contains the definition of multiple tagged deployment
scenarios.  During assembly Merlin will attempt to locate an explicit deployment profile (a
component declaration in the block.xml).  In no explicit profile is available Merlin will
select a packaged profile based on the xprofile declarations, otherwise Merlin will attempt
to construct an implicit profile.
           </p>
           <p><i>RandomGeneratorProvider.xprofile</i></p>
   <source><![CDATA[
  @@ -112,8 +96,7 @@
   $ merlin build\classes
           </source>
           <p>
  -        In the logging output we see that Merlin has automatically
  -        locating the RandomGeneratorProvider using the packaged profile.
  +In the logging output we see that Merlin has automatically locating the RandomGeneratorProvider
using the packaged profile.
           </p>
   <source>
   [INFO   ] (tutorial.hello.random-provider#randomizer): configuration stage
  @@ -121,17 +104,13 @@
   [INFO   ] (tutorial.hello): random: 6608684
   </source>
           <p>
  -        Note: When constructing an name for the component based on a 
  -        packaged profile, Merlin will append the component type name to the 
  -        profile name, seperated by the # character resulting in the 
  -        compoennt name 'random-provider#randomizer'.
  +Note: When constructing an name for the component based on a packaged profile, Merlin will
append the component type name to the profile name, seperated by the # character resulting
in the component name 'random-provider#randomizer'.
           </p>
   
         </subsection>
         <subsection name="Profile selection">
           <p>
  -        The <a href="selectors.html">next tutorial</a> describes the 
  -        mechansims used to influence profile selection within Merlin. 
  +The <a href="selectors.html">next tutorial</a> describes the mechanisms used
to influence profile selection within Merlin. 
           </p>
         </subsection>
   
  
  
  
  1.3       +3 -15     avalon-sandbox/merlin/merlin-smp/xdocs/starting/advanced/selectors.xml
  
  Index: selectors.xml
  ===================================================================
  RCS file: /home/cvs/avalon-sandbox/merlin/merlin-smp/xdocs/starting/advanced/selectors.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- selectors.xml	5 Apr 2003 11:54:27 -0000	1.2
  +++ selectors.xml	8 Apr 2003 11:51:00 -0000	1.3
  @@ -11,20 +11,10 @@
       <section name="Advanced Features">
         <subsection name="Profile Selection">
           <p>
  -          In the <a href="profiles.html">Profile tutorial</a> we covered the

  -          mechanisms used to establish a set of preconfigured deployment 
  -          profiles.  Generally speaking the combination of profile overriding 
  -          in the block.xml &lt;component&gt; directive, packaged profiles, 
  -          and default configurations is sufficient.  However, mechanisms are 
  -          provided for the introduction of profile selection policy.  In this
  -          tutorial we include multiple deployment profiles to the random 
  -          generator component and we define a custom profile selector.  The 
  -          selector is declatred to Merlin as an attribute of the dependency 
  -          declared by the consuming component (HelloComponent). 
  +In the <a href="profiles.html">Profile tutorial</a> we covered the mechanisms
used to establish a set of pre-configured deployment profiles.  Generally speaking the combination
of profile overriding in the block.xml &lt;component&gt; directive, packaged profiles,
and default configurations is sufficient.  However, mechanisms are provided for the introduction
of profile selection policy.  In this tutorial we include multiple deployment profiles to
the random generator component and we define a custom profile selector.  The selector is declared
to Merlin as an attribute of the dependency declared by the consuming component (HelloComponent).

           </p>
           <p>
  -          Component deployment profiles are co-located with the component
  -          implementation class under a .xprofile resource.
  +Component deployment profiles are co-located with the component implementation class under
an .xprofile resource.
           </p>
         </subsection>
         <subsection name="Adding multiple profiles">
  @@ -165,9 +155,7 @@
   $ merlin build\classes
           </source>
           <p>
  -        In the logging output we see that Merlin has selected the profile
  -        with the highest seed value (the profile selection criteria implemented
  -        by our custom selector).
  +In the logging output we see that Merlin has selected the profile with the highest seed
value (the profile selection criteria implemented by our custom selector).
           </p>
   <source>
   [INFO   ] (sys.profiles.selector): available profile: random-provider#primary
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org


Mime
View raw message