cvs commit: jakarta-avalon-excalibur/assembly/src/etc infomover.xml

[mc...@apache.org]

mcconnell    2002/08/22 09:44:01

  Added:       assembly/lib cornerstone.jar excalibur-pool-1.0.jar
                        excalibur-thread-1.0.jar phoenix-client.jar
               assembly/src/etc infomover.xml
  Log:
  Temporary update to facilitate the infomover demo - to execute, cd to
  the excalibur/assembly directory and ....
  
    $ merlin src\etc\infomover.xml
  
  Revision  Changes    Path
  1.1                  jakarta-avalon-excalibur/assembly/lib/cornerstone.jar
  
  	<<Binary file>>
  
  
  1.1                  jakarta-avalon-excalibur/assembly/lib/excalibur-pool-1.0.jar
  
  	<<Binary file>>
  
  
  1.1                  jakarta-avalon-excalibur/assembly/lib/excalibur-thread-1.0.jar
  
  	<<Binary file>>
  
  
  1.3       +162 -181  jakarta-avalon-excalibur/assembly/lib/phoenix-client.jar
  
  	<<Binary file>>
  
  
  1.1                  jakarta-avalon-excalibur/assembly/src/etc/infomover.xml
  
  Index: infomover.xml
  ===================================================================
  
  <!--
  Test kernel hosting the infomover components
  -->
  
  <kernel>
  
     <!-- 
     Just log to the screen (default) - change the taget to "infomover" to 
     create an infomover.log file
     -->
  
     <logging priority="INFO" target="default">
        <category priority="ERROR"  name="logging" />
        <target name="timinfomover">
          <file location="infomover.log" />
        </target>
     </logging>
  
     <!--
     Create a container holding the cornerstone components that we actually need 
     to declare explicitly (the stuff that needs explicit configuration info).
     -->
  
     <container name="cornerstone">
  
       <!--
       Corenerstone stuff is not the subject of this demo so set the 
       priority to INFO as the default for the container, and put classloader
       and kernel logging up on ERROR level so we only see problems.
       -->
  
       <categories priority="INFO">
         <category priority="ERROR"  name="kernel" />
         <category priority="ERROR"  name="loader" />
       </categories>
  
       <!--
       Create a classloader containging the cornerston jar file.  This is 
       a special version that includes .xtype meta-info declarations.  Include
       the phoenix client jar file (also special - contains the GenericBlockContext
       which is needed to work around container specific references in conerstone 
       blocks.  The thread and pool jars are needed due to undeclared depedencies 
       from the conternstone jar file.
       -->
  
       <classpath>
         <fileset dir="lib">
           <include name="cornerstone.jar"/>
           <include name="phoenix-client.jar"/>
           <include name="excalibur-thread-1.0.jar"/>
           <include name="excalibur-pool-1.0.jar"/>
         </fileset>
       </classpath>
  
       <!-- 
       let merlin build a connection and thread managers automatically because
       neither of these require a configuration so Merlin can figure everything out
       itself
       -->
  
       <!-- 
       declare the socket manager bacause the socket manager actually needs a 
       configuration and context directives to work around the Phoenix BlockContext
       references 
       -->
  
       <component name="sockets" 
           class="org.apache.avalon.cornerstone.blocks.sockets.DefaultSocketManager" activation="false">
  
         <!--
         this is where we twll Merlin how to do the context creation - one entry is 
         imported from the kernel (the base directory), and the other entry is declared
         directly (the component name)
         -->
  
         <context class="org.apache.avalon.phoenix.tools.export.GenericBlockContext">
           <import key="app.home" name="avalon:home"/>
           <entry key="block.name" value="store"/>
         </context>
  
         <!--
         provide the configuration
         -->
  
         <configuration>
           <server-sockets>
             <factory name="plain" 
               class="org.apache.avalon.cornerstone.blocks.sockets.DefaultServerSocketFactory"/>
           </server-sockets>
           <client-sockets>
             <factory name="plain" 
               class="org.apache.avalon.cornerstone.blocks.sockets.DefaultSocketFactory"/>
           </client-sockets>
         </configuration>
  
       </component>
  
       <!-- 
       create a subcontainer containing the infomover stuff - no particular reason for a 
       sub-container hee but why not .... it's a demo isn't it? - besides we can switch
       default logging catagories to DEBUG which means we will only see infomover messages
       which is convinient
       -->
  
       <container name="infomover">
  
         <categories priority="DEBUG">
           <category priority="ERROR"  name="loader" />
         </categories>
  
         <!--
         declare the classpath additions for the classloader
         -->
  
         <classpath>
           <fileset dir="../../jakarta-avalon-apps/infomover/build/lib">
             <include name="infomover.jar"/>
           </fileset>
         </classpath>
  
         <!--
         add the connection manager and make it startup when the container starts
         -->
  
         <component name="connections" 
            class="org.apache.infomover.connection.impl.ConnectionManagerImpl" 
            activation="true">
         </component>
  
         <!--
         add the job manager and make it startup when the container starts
         -->
  
         <component name="job-manager" 
            class="org.apache.infomover.jobmanager.impl.JobManagerImpl" 
            activation="true">
         </component>
  
      </container>
  
    </container>
  
  </kernel>
  
  
  

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>