commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jstrac...@apache.org
Subject cvs commit: jakarta-commons-sandbox/messenger/src/conf SpiritWave.xml test-connections.xml Messenger.xml
Date Tue, 30 Oct 2001 08:30:09 GMT
jstrachan    01/10/30 00:30:09

  Modified:    messenger PROPOSAL.html STATUS.html build.properties.sample
                        build.xml
               messenger/src/conf Messenger.xml
  Added:       messenger/src/conf SpiritWave.xml test-connections.xml
  Log:
  Modified build system so that to build messenger only the JMS and Servlet APIs are required
and that J2EE SDK is only required for building the unit tests. The sample web application
can be configured to run against any JMS implementation
  
  Revision  Changes    Path
  1.5       +10 -7     jakarta-commons-sandbox/messenger/PROPOSAL.html
  
  Index: PROPOSAL.html
  ===================================================================
  RCS file: /home/cvs/jakarta-commons-sandbox/messenger/PROPOSAL.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- PROPOSAL.html	2001/08/28 22:38:28	1.4
  +++ PROPOSAL.html	2001/10/30 08:30:09	1.5
  @@ -10,10 +10,9 @@
   
   <h3>(0) Rationale</h3>
   <p>
  -  The Messenger library provides a simple facade over the JMS API
  -  making it easy to use JMS from inside servlets and JSP tag libraries.
  -  Messenger also provides a standard servlet for sending and receiving
  -  messages from JMS.
  +<p>The <em>Messenger</em> package provides a framework for working with
JMS
  +on the servlet platform. <em>Messenger</em> provides a simple and easy to use
facade over
  +the JMS API hiding much of the complexities of the JMS API.
   </p>
   <p>
     Messenger employs a simple session based pooling technique such that a 
  @@ -36,7 +35,7 @@
   <h3>(1.5) Interaction With Other Packages</h3>
   
   <p><em>Messenger</em> relies on standard JDK 1.2 (or later) APIs for
  -production deployment along with the JMS API and the JNDI API.
  +production deployment along with the JMS API, JNDI API and the Servlet API.
   </p>
   
   <p><em>Messenger</em> also uses the Jakarta Digester package, 
  @@ -45,12 +44,16 @@
   
   <p>Messsenger utilizes the JUnit unit testing framework for
   developing and executing unit tests, but this is of interest only to
  -developers of the component.  
  +developers of the component.   
   </p>
   
  -<p>In addition the build and JUnit testing framework all rely on 
  +<p>In addition the JUnit testing framework relies on the 
   J2EE SDK (1.3 or later) as the reference implementation of 
   JMS and JNDI to test against.</p>
  +
  +<p>There is an example web application that demonstrates
  +Messenger, MDO and Messagelets in action which can be built
  +against any JMS provider.</p>
   
   
   <h3>(2) Initial Source of the Package</h3>
  
  
  
  1.5       +19 -12    jakarta-commons-sandbox/messenger/STATUS.html
  
  Index: STATUS.html
  ===================================================================
  RCS file: /home/cvs/jakarta-commons-sandbox/messenger/STATUS.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- STATUS.html	2001/08/28 22:38:28	1.4
  +++ STATUS.html	2001/10/30 08:30:09	1.5
  @@ -7,7 +7,7 @@
   
   <div align="center">
   <h1>The Jakarta Commons <em>Messenger</em> Package</h1>
  -$Id: STATUS.html,v 1.4 2001/08/28 22:38:28 jstrachan Exp $<br>
  +$Id: STATUS.html,v 1.5 2001/10/30 08:30:09 jstrachan Exp $<br>
   <a href="#Introduction">[Introduction]</a>
   <a href="#Dependencies">[Dependencies]</a>
   <a href="#Release Info">[Release Info]</a>
  @@ -20,12 +20,13 @@
   <a name="Introduction"></a>
   <h3>1.  INTRODUCTION</h3>
   
  -<p>The <em>Messenger</em> package provides a simple facade over the JMS
API
  - making it easy to use JMS from inside servlets and JSP tag libraries as
  -well as providing a standard servlet for sending and receiving messages on JMS.
  +<p>The <em>Messenger</em> package provides a framework for working with
JMS
  +on the servlet platform. <em>Messenger</em> provides a simple and easy to use
facade over
  +the JMS API implementing session pooling and hiding much of the 
  +complexities of the JMS API.
   </p>
   <p<em>Messenger</em> also provides a simple XML deployment descriptor for

  -configuring all JMS connections and sessions making it easy to work with JMS.
  +configuring all JMS connections and sessions making it very easy to work with JMS.
   </p>
   <p>
   The following classes are included:</p>
  @@ -43,7 +44,7 @@
   <h3>2.  DEPENDENCIES</h3>
   
   <p>The <em>Messenger</em> package is dependent upon the following external
  -components for development and use:</p>
  +components for building:</p>
   <ul>
   <li><a href="http://java.sun.com/j2se">Java Development Kit</a>
       (Version 1.2 or later)</li>
  @@ -53,17 +54,23 @@
     Jakarta Commons BeanUtils</a></li>
   <li><a href="http://jakarta.apache.org/commons/collections.html">
     Jakarta Commons Collections</a></li>
  -<li><a href="http://java.sun.com/products/jndi">JNDI</a>
  -    (Version 1.1 or later) which ships with JDK version 1.3 or later 
  -    - required for deployment</li>
   <li><a href="http://java.sun.com/products/jms">JMS</a>
  -    (Version 1.0.2b or later) 
  -    - required for deployment</li>
  +    (Version 1.0.2b or later)</li>
  +<li><a href="http://java.sun.com/products/servlet">Servlet</a>
  +    (Version 2.3 or later)</li>
  +<li><a href="http://java.sun.com/products/jndi">JNDI</a>
  +    (Version 1.1 or later) which ships with JDK version 1.3 or later</li>
  +</ul>
  +
  +<p>The <em>Messenger</em> package is dependent upon the following external
  +components for unit tests only:</p>
  +
  +<ul>
   <li><a href="http://www.junit.org">JUnit Testing Framework</a>
       (Version 3.7 or later) - for unit tests only, not required
       for deployment</li>
   <li><a href="http://java.sun.com/j2ee">J2EE Development Kit</a>
  -    (Version 1.3 or later) - for build and unit tests only, not required
  +    (Version 1.3 or later) - for unit tests only, not required
       for deployment</li>
   </ul>
   
  
  
  
  1.12      +17 -8     jakarta-commons-sandbox/messenger/build.properties.sample
  
  Index: build.properties.sample
  ===================================================================
  RCS file: /home/cvs/jakarta-commons-sandbox/messenger/build.properties.sample,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- build.properties.sample	2001/10/30 07:47:10	1.11
  +++ build.properties.sample	2001/10/30 08:30:09	1.12
  @@ -1,11 +1,10 @@
  -# junit.jar - JUnit 3.2+ Classpath
  -junit.jar=/java/junit/junit.jar
  +#
  +# Compile-time dependencies
  +#
   
  -# j2sdkee installation
  -j2sdkee=/j2sdkee1.3
  +jms.jar=/jpackages/jms1.0.2b/lib/jms.jar
   
  -# catalina.jar
  -#catalina.jar=../../lib/catalina.jar
  +servlet.jar=../../lib/servlet.jar
   
   # jakarta commons-digester.jar
   commons-digester.jar=../../jakarta-commons/digester/dist/commons-digester.jar
  @@ -16,6 +15,18 @@
   # jakarta commons-beanutils.jar
   commons-beanutils.jar=../../jakarta-commons/beanutils/dist/commons-beanutils.jar
   
  +
  +
  +#
  +# Runtime dependencies
  +#
  +
  +# junit.jar - JUnit 3.2+ Classpath
  +junit.jar=/java/junit/junit.jar
  +
  +# j2sdkee installation
  +j2sdkee=/j2sdkee1.3
  +
   # Messenger deployment config to use in tests, defaults to Suns RI
   messenger.xml=src/conf/Messenger.xml
   
  @@ -26,5 +37,3 @@
   # Directory where the JMS classes or properties files reside 
   # which are copied to WEB-INF/classes
   jms.classes.dir=conf
  -
  -
  
  
  
  1.20      +11 -5     jakarta-commons-sandbox/messenger/build.xml
  
  Index: build.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons-sandbox/messenger/build.xml,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- build.xml	2001/10/30 07:47:10	1.19
  +++ build.xml	2001/10/30 08:30:09	1.20
  @@ -1,4 +1,4 @@
  -<!-- $Id: build.xml,v 1.19 2001/10/30 07:47:10 jstrachan Exp $ -->
  +<!-- $Id: build.xml,v 1.20 2001/10/30 08:30:09 jstrachan Exp $ -->
   <project name="messenger" default="test" basedir=".">
   
      <!-- patternset describing files to be copied from the doc directory -->
  @@ -49,8 +49,11 @@
         <property name="j2ee.jar" value="${j2sdkee}/lib/j2ee.jar"/>
   
         <!-- now combine the classpaths -->
  -      <property name="classpath" value="${cp}:${j2ee.jar}:${j2sdkee}/lib/local:${commons-digester.jar}:${commons-collections.jar}:${commons-beanutils.jar}:${junit.jar}"/>
  +      <property name="classpath" value="${cp}:${jms.jar}:${servlet.jar}:${commons-digester.jar}:${commons-collections.jar}:${commons-beanutils.jar}"/>
   
  +      <!-- classpath for unit tests -->
  +      <property name="test.classpath" value="${cp}:${j2ee.jar}:${j2sdkee}/lib/local}:${junit.jar}:${commons-digester.jar}:${commons-collections.jar}:${commons-beanutils.jar}"/>
  +
         <property name="name" value="messenger"/>
         <property name="Name" value="Commons Messenger"/>
         <property name="Name-Long" value="Jakarta Commons Messenger Package"/>
  @@ -216,7 +219,7 @@
         <mkdir dir="${dest.classes}"/>
         <javac destdir="${dest.classes}"
                srcdir="${source.src.test}"
  -             classpath="${classpath}"
  +             classpath="${test.classpath}"
                debug="false"
                deprecation="true"
                optimize="true"/>
  @@ -292,17 +295,20 @@
         -->
   
         <java classname="${test.runner}" fork="yes" failonerror="${test.failonerror}">
  -        <arg value="${test.entry}"/>
           <classpath>
             <pathelement location="${dest.classes}" />
  -          <pathelement path="${classpath}" />
  +          <pathelement path="${test.classpath}"/>
             <pathelement path="${java.class.path}" />
           </classpath>
  +
  +        <arg value="${test.entry}"/>
  +
           <!-- J2EE SDK properties -->
           <sysproperty key="jms.properties" value="${j2sdkee}/config/jms_client.properties"/>
           <sysproperty key="java.security.policy" value="${j2sdkee}/lib/security/client.policy"/>
           <sysproperty key="java.security.auth.login.config" value="${j2sdkee}/lib/security/login.config"/>
           <sysproperty key="com.sun.enterprise.home" value="${j2sdkee}"/>
  +        <sysproperty key="org.apache.commons.messenger" value="${source.src.conf}/test-connections.xml"/>
         </java>
      </target>
   
  
  
  
  1.3       +1 -0      jakarta-commons-sandbox/messenger/src/conf/Messenger.xml
  
  Index: Messenger.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons-sandbox/messenger/src/conf/Messenger.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- Messenger.xml	2001/10/15 20:04:07	1.2
  +++ Messenger.xml	2001/10/30 08:30:09	1.3
  @@ -2,6 +2,7 @@
   <manager>
   
     <!-- this example Messenger XML config file should work with J2EE SDK -->
  +  <!-- when running inside of a J2EE container                          -->
   
     <messenger name="topic">
       <jndi lookupName="java:comp/env/TopicConnectionFactory">
  
  
  
  1.1                  jakarta-commons-sandbox/messenger/src/conf/SpiritWave.xml
  
  Index: SpiritWave.xml
  ===================================================================
  <?xml version="1.0" encoding="UTF-8"?>
  <manager>
  
    <!-- Embedded JMQ daemons -->
    <messenger name="topic">
      <factory className="com.spirit.messenger.WaveTopicSessionFactory">
        <property>
          <name>driverName</name>
          <value>SpiritJMQ</value>
        </property>          
        <property>
          <name>messageChannels</name>	
          <value>stream://localhost:3345</value>
        </property>          
        <property>
          <name>dispatchThreadPerConnection</name>	
          <value>true</value>
        </property>          
      </factory>
    </messenger>
  
    <messenger name="queue">
      <factory className="com.spirit.messenger.WaveQueueSessionFactory">
        <property>
          <name>driverName</name>
          <value>SpiritJMQ</value>
        </property>          
        <property>
          <name>messageChannels</name>	
          <value>stream://localhost:3345</value>
        </property>          
        <property>
          <name>dispatchThreadPerConnection</name>	
          <value>true</value>
        </property>          
      </factory>
    </messenger>
  
  </manager>
  
  
  
  1.1                  jakarta-commons-sandbox/messenger/src/conf/test-connections.xml
  
  Index: test-connections.xml
  ===================================================================
  <?xml version="1.0" encoding="UTF-8"?>
  <manager>
  
    <!-- this example Messenger XML config file should work with J2EE SDK -->
    <!-- when running outside of a J2EE container                         -->
  
    <messenger name="topic">
      <jndi lookupName="TopicConnectionFactory">
        <property>
          <name>com.sun.jms.internal.java.naming.factory.initial</name>
          <value>com.sun.enterprise.naming.SerialInitContextFactory</value>
        </property>          
      </jndi>
    </messenger>
  
    <messenger name="queue">
      <jndi lookupName="QueueConnectionFactory">
        <property>
          <name>com.sun.jms.internal.java.naming.factory.initial</name>
          <value>com.sun.enterprise.naming.SerialInitContextFactory</value>
        </property>          
      </jndi>
    </messenger>
  
  </manager>
  
  
  

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message