jmscts-cvs Mailing List for JMS CTS (Page 22)
Status: Alpha
Brought to you by:
tanderson
Menu
▾
▴
jmscts-cvs — The JMS CTS cvs commit list
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(51) |
Jun
(69) |
Jul
(191) |
Aug
(7) |
Sep
(38) |
Oct
(41) |
Nov
|
Dec
(8) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(26) |
Feb
(69) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(25) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <tan...@us...> - 2003-05-28 15:08:42
|
Update of /cvsroot/jmscts/jmscts/src/schemas In directory sc8-pr-cvs1:/tmp/cvs-serv25970/src/schemas Removed Files: provider.xsd Log Message: removed redundant schema --- provider.xsd DELETED --- |
|
From: <tan...@us...> - 2003-05-28 15:06:59
|
Update of /cvsroot/jmscts/jmscts/src/java/org/exolab/jmscts/util In directory sc8-pr-cvs1:/tmp/cvs-serv25205/src/java/org/exolab/jmscts/util Log Message: Directory /cvsroot/jmscts/jmscts/src/java/org/exolab/jmscts/util added to the repository |
|
From: <tan...@us...> - 2003-05-28 15:06:29
|
Update of /cvsroot/jmscts/jmscts/src/schemas
In directory sc8-pr-cvs1:/tmp/cvs-serv25004/src/schemas
Modified Files:
coverage.xsd
Log Message:
changes to reflect removal of provider.xsd
Index: coverage.xsd
===================================================================
RCS file: /cvsroot/jmscts/jmscts/src/schemas/coverage.xsd,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** coverage.xsd 4 May 2003 14:12:40 -0000 1.1
--- coverage.xsd 28 May 2003 15:06:25 -0000 1.2
***************
*** 6,11 ****
targetNamespace="http://openjms.sourceforge.net/jmscts/coverage">
- <xsd:import namespace="http://openjms.sourceforge.net/jmscts/provider"
- schemaLocation="provider.xsd"/>
<xsd:import namespace="http://openjms.sourceforge.net/jmscts/types"
schemaLocation="types.xsd"/>
--- 6,9 ----
***************
*** 29,33 ****
<xsd:complexType>
<xsd:sequence>
! <xsd:element ref="provider:proxy" />
<xsd:element ref="currentTest" minOccurs="0" />
<xsd:element ref="coverage" maxOccurs="unbounded" />
--- 27,31 ----
<xsd:complexType>
<xsd:sequence>
! <xsd:element name="provider" type="xsd:string" />
<xsd:element ref="currentTest" minOccurs="0" />
<xsd:element ref="coverage" maxOccurs="unbounded" />
|
|
From: <tan...@us...> - 2003-05-26 14:11:23
|
Update of /cvsroot/jmscts/jmscts/src/xdocs/images In directory sc8-pr-cvs1:/tmp/cvs-serv8405 Added Files: jmscts.gif Log Message: added project logo --- NEW FILE: jmscts.gif --- (This appears to be a binary file; contents omitted.) |
|
From: <tan...@us...> - 2003-05-26 14:10:28
|
Update of /cvsroot/jmscts/jmscts In directory sc8-pr-cvs1:/tmp/cvs-serv7868 Added Files: checkstyle.properties Log Message: added checkstyle configuration --- NEW FILE: checkstyle.properties --- # Exolab conventions are similar to Sun's, with a few tweaks # skip CVS tags checkstyle.ignore.maxlinelen = ^.*\\$Id.*$ checkstyle.wrap.operator = eol checkstyle.pattern.const = log|^[A-Z](_?[A-Z0-9]+)*$ checkstyle.pattern.member = ^_?[a-z][a-zA-Z0-9]*$ checkstyle.pattern.static = ^_?[a-z][a-zA-Z0-9]*$ |
|
From: <tan...@us...> - 2003-05-26 13:17:39
|
Update of /cvsroot/jmscts/jmscts/src/xdocs
In directory sc8-pr-cvs1:/tmp/cvs-serv16477/src/xdocs
Added Files:
changes.xml index.xml install.xml navigation.xml status.xml
using.xml
Log Message:
initial cut of a mavenized build
--- NEW FILE: changes.xml ---
<?xml version="1.0"?>
<document>
<properties>
<title>Changes</title>
<author email="tm...@ne...">Tim Anderson</author>
</properties>
<body>
<release version="0.5" date="in CVS">
<action dev="tima" type="update">
Changed license to the Exolab Project license
</action>
</release>
<release version="0.4" date="2001-11-19">
<action dev="tima" type="add">
Added greater coverage of the specification. The
CTS now covers approximately 80% of the specification
and executes over 15000 test cases
</action>
</release>
<release version="0.3" date="2001-10-24">
<action dev="tima" type="add">
Added support for stress testing
</action>
<action dev="tima" type="update">
Now generate compliance reports in HTML
</action>
</release>
<release version="0.2" date="2001-10-7">
<action dev="tima" type="add">
Added coverage of the JMS selector and queue browser APIs
</action>
<action dev="tima" type="add">
Added utility to take a coverage report snapshot while the
JMS CTS is running
</action>
<action dev="tima" type="add">
Added functions to stop and abort the JMS CTS
</action>
</release>
<release version="0.1" date="2001-9-13">
<action dev="tima" type="add">
The initial release of the JMS CTS. This includes the following
features:
<ul>
<li>Coverage of the JMS message, session, producer, consumer and
connection APIs</li>
<li>Compliance reports, generated in XML</li>
<li>Simple interface to plug in different JMS implementations</li>
<li>Complete automation, to support regression testing</li>
<li>Test case filtering, to narrow testing to help locate problem
areas</li>
</ul>
</action>
</release>
</body>
</document>
--- NEW FILE: index.xml ---
<?xml version="1.0"?>
<document>
<properties>
<title>Welcome</title>
</properties>
<body>
<section name="What is the JMS Compliance Test Suite?">
<p>The JMS Compliance Test Suite is a test harness for exercising
Java Message Service (JMS) implementations to:
<ul>
<li>Simplify evaluation of JMS implementations</li>
<li>Determine the level of compliance with the JMS specification of
an implementation</li>
<li>Help identify bugs in an implementation</li>
</ul>
</p>
<p>
Its features include:
<ul>
<li>Comprehensive coverage of the JMS API</li>
<li>Compliance reports</li>
<li>Simple interface to plug in different JMS implementations</li>
<li>Complete automation, to support regression testing</li>
<li>Test case filtering, to narrow testing to help locate problem
areas</li>
<li>Stress testing</li>
</ul>
</p>
</section>
</body>
</document>
--- NEW FILE: install.xml ---
<?xml version="1.0"?>
<document>
<properties>
<title>Download/Installation</title>
</properties>
<body>
<section name="Download/Installation">
<subsection name="Requirements">
<p>
The JMS CTS will run on any platform where there is a suitable
<a href="http://java.sun.com/j2se/">Java 2 runtime environment</a>.
</p>
</subsection>
<subsection name="Downloading JMS CTS">
<p>
The latest stable version of JMS CTS is available from the
<a href="http://sourceforge.net/project/showfiles.php?group_id=81568">SourceForge download page</a>.
</p>
</subsection>
</section>
</body>
</document>
--- NEW FILE: navigation.xml ---
<?xml version="1.0" encoding="ISO-8859-1"?>
<project name="JMS CTS" href="http://jmscts.sourceforge.net">
<title>JMS CTS: The JMS Compliance Test Suite</title>
<body>
<links>
<item name="Home Page" href="http://jmscts.sourceforge.net/"/>
<item name="SourceForge Project Page"
href="http://sourceforge.net/projects/jmscts/"/>
<item name="JMS" href="http://java.sun.com/jms/"/>
</links>
<menu name="JMS CTS">
<item name="Overview" href="/index.html"/>
<item name="News and Status" href="/status.html"/>
<item name="Download/Installation" href="/install.html"/>
<item name="Using JMS CTS" href="/using.html"/>
</menu>
</body>
</project>
--- NEW FILE: status.xml ---
<?xml version="1.0"?>
<document>
<properties>
<title>News and Status</title>
</properties>
<body>
<section name="News and Status">
<p>
This document contains the latest news and status regarding the
JMS CTS project.
It is here you'll find announcements related to JMS CTS.
</p>
<subsection name="Current Status">
<p>
We are currently working on JMS CTS 0.5.
</p>
</subsection>
<subsection name="May, 2003: JMS CTS moves">
<p>
The JMS CTS has moved to a new home,
<a href="http://jmscts.sourceforge.net">
http://jmscts.sourceforge.net</a>. <br/>
It was originally part of the <a href="openjms.sourceforge.net">
OpenJMS</a> project.
</p>
</subsection>
</section>
</body>
</document>
--- NEW FILE: using.xml ---
<?xml version="1.0"?>
<document>
<properties>
<title>Using JMS CTS</title>
</properties>
<body>
<section name="Using JMS CTS">
<p>
In order to use JMS CTS, the following are required:
<ul>
<li>A JMS provider.</li>
<li>A proxy to enable the JMS CTS to connect to, and administer, the
JMS provider</li>
<li>A configuration file to enable the JMS CTS to locate the
proxy classes</li>
</ul>
These are discussed in the following sections.
</p>
<subsection name="JMS Providers">
<p>
There are a plethora of JMS providers available, both commercial
and opensource, some of which are listed below:
<table>
<tr>
<td><a href="http://openjms.sourceforge.net/">OpenJMS</a></td>
</tr>
<tr>
<td><a href="http://jboss.org/">JBossMQ</a></td>
</tr>
<tr>
<td><a href="http://joram.objectweb.org/">JORAM</a></td>
</tr>
<tr>
<td><a href="http://www.sonicsoftware.com/">SonicMQ</a></td>
</tr>
<tr>
<td><a href="http://www.swiftmq.com/">SwiftMQ</a></td>
</tr>
<tr>
<td><a href="http://www.fiorano.com/">FioranoMQ</a></td>
</tr>
<tr>
<td><a href="http://www.softwired-inc.com/">
iBus//MessageServer</a>
</td>
</tr>
</table>
</p>
</subsection>
<subsection name="Proxies">
<p>
The JMS CTS requires a set of proxy classes to connect to a JMS
provider and administer it.
</p>
<p>
These are needed as the JMS specification does not mandate how a
JMS provider should be connected to, or administered.
</p>
<p>
The JMS CTS is distributed with sample proxies for the Sun JMS
reference implementation,
<a href="http://www.openjms.org">OpenJMS</a>,
<a href="http://www.fiorano.com">FioranoMQ</a> and
<a href="http://www.softwired-inc.com">iBus//MessageServer</a>.
These can be used as guides when developing proxies for other JMS
implementations.
</p>
</subsection>
<subsection name="JMS CTS Configuration">
<p>
<source><![CDATA[
<?xml version="1.0"?>
<configuration>
<provider>
<name>OpenJMS</name>
<class>org.exolab.jmscts.openjms.OpenJMSProvider</class>
<paths>
<path>${jmscts.home}/lib/openjms_provider-0.5-dev.jar</path>
<path>${openjms.home}/lib/openjms-0.7.6-dev.jar</path>
</paths>
<config>
<path>${openjms.home}/config/openjms.xml</path>
</config>
</provider>
</configuration>
]]></source>
</p>
</subsection>
</section>
</body>
</document>
|
|
From: <tan...@us...> - 2003-05-26 13:17:39
|
Update of /cvsroot/jmscts/jmscts
In directory sc8-pr-cvs1:/tmp/cvs-serv16477
Added Files:
maven.xml project.properties project.xml
Log Message:
initial cut of a mavenized build
--- NEW FILE: maven.xml ---
<project default="jar:jar"
xmlns:ant="jelly:ant"
xmlns:castor="castor"
xmlns:deploy="deploy"
xmlns:j="jelly:core"
xmlns:maven="maven"
xmlns:util="jelly:util">
<preGoal name="java:compile">
<!-- generate java sources using castor -->
<attainGoal name="castor:prepare-filesystem"/>
<ant:echo message="here"/>
<castor:generate schema="src/schemas/foo.xsd"
package="foo"
types="j2"/>
<castor:generate schema="src/schemas/bar.xsd"
package="bar"
types="j2"/>
<castor:generate schema="src/schemas/types.xsd"
package="org.exolab.jmscts.core"
types="j2"/>
<castor:generate schema="src/schemas/properties.xsd"
package="org.exolab.jmscts.core"
types="j2"/>
<castor:generate schema="src/schemas/provider.xsd"
package="org.exolab.jmscts.provider"
types="j2"/>
<castor:generate schema="src/schemas/filter.xsd"
package="org.exolab.jmscts.core.filter"
types="j2"/>
<castor:generate schema="src/schemas/requirements.xsd"
package="org.exolab.jmscts.requirements"
types="j2"/>
<castor:generate schema="src/schemas/coverage.xsd"
package="org.exolab.jmscts.coverage"
types="j2"/>
<castor:generate schema="src/schemas/stress.xsd"
package="org.exolab.jmscts.stress.config"
types="j2"/>
<castor:generate schema="src/schemas/statistics.xsd"
package="org.exolab.jmscts.stress"
types="j2"/>
<castor:generate schema="src/schemas/selector.xsd"
package="org.exolab.jmscts.test.selector"
types="j2"/>
</preGoal>
<!-- create the lib and bin directories in the binary distro -->
<preGoal name="dist:build-bin">
<j:set var="dist.dir" value="${maven.dist.bin.assembly.dir}"/>
<mkdir dir="${dist.dir}/bin"/>
<!--mkdir dir="${dist.dir}/lib"/-->
<copy todir="${dist.dir}/bin">
<fileset dir="src/bin"/>
</copy>
<!--chmod file="${dist.dir}/bin/jmscts" perm="ugo+rx" /-->
<!-- copy the dependencies -->
<deploy:copy-deps todir="${dist.dir}/lib"/>
<!-- move the jmscts jar to the right dir - gets placed in root
by dist:prepare-bin-filesystem -->
<ant:move file="${dist.dir}/${maven.final.name}.jar"
todir="${dist.dir}/lib"/>
</preGoal>
</project>
--- NEW FILE: project.properties ---
# -------------------------------------------------------------------
# P R O J E C T P R O P E R T I E S
# -------------------------------------------------------------------
# -------------------------------------------------------------------
# C H E C K S T Y L E P R O P E R T I E S
# -------------------------------------------------------------------
maven.checkstyle.properties = ${basedir}/checkstyle.properties
# -------------------------------------------------------------------
# D O C P R O P E R T I E S
# -------------------------------------------------------------------
maven.docs.src = ${basedir}/src/xdocs
maven.ui.banner.background = #fff
# Display the date on the JMS CTS web site
maven.xdoc.date = left
# Display the JMS CTS version the web site is documenting
maven.xdoc.version = ${pom.currentVersion}
--- NEW FILE: project.xml ---
<?xml version="1.0" encoding="ISO-8859-1"?>
<project>
<pomVersion>3</pomVersion>
<name>JMS Compliance Test Suite</name>
<id>jmscts</id>
<currentVersion>0.5-dev</currentVersion>
<inceptionYear>2001</inceptionYear>
<organization>
<name>JMS CTS Team</name>
<url>http://jmscts.sourceforge.net/</url>
<logo>/images/jmscts.gif</logo>
</organization>
<logo>http://sourceforge.net/sflogo.php?group_id=81568&type=5</logo>
<package>org.exolab.jmscts</package>
<packageGroups>
<packageGroup>
<title>Core Public API</title>
<packages>org.exolab.jmscts.core</packages>
</packageGroup>
<packageGroup>
<title>Requirements</title>
<packages>org.exolab.jmscts.requirements</packages>
</packageGroup>
<packageGroup>
<title>JMS Provider Adapter</title>
<packages>org.exolab.jmscts.provider</packages>
</packageGroup>
<packageGroup>
<title>Compliance Tests</title>
<packages>org.exolab.jmscts.test</packages>
</packageGroup>
<packageGroup>
<title>Stress Test API</title>
<packages>org.exolab.jmscts.stress</packages>
</packageGroup>
</packageGroups>
<shortDescription>JMS Compliance Test Suite</shortDescription>
<!-- Gump integration -->
<gumpRepositoryId>jmscts</gumpRepositoryId>
<url>http://jmscts.sourceforge.net</url>
<issueTrackingUrl>http://sourceforge.net/tracker/?group_id=81568</issueTrackingUrl>
<siteAddress>jmscts.sourceforge.net</siteAddress>
<siteDirectory>/home/groups/j/jm/jmscts/htdocs/</siteDirectory>
<!--distributionDirectory>/home/groups/j/jm/jmscts/htdocs/distributions/</distributionDirectory-->
<repository>
<connection>scm:cvs:pserver:an...@cv...:/cvsroot/jmscts:jmsctstests</connection>
<url>http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jmscts/jmsctstests/</url>
</repository>
<versions>
</versions>
<branches>
</branches>
<mailingLists>
<mailingList>
<name>JMS CTS User List</name>
<subscribe>jms...@li...</subscribe>
<unsubscribe>jms...@li...</unsubscribe>
<archive>http://sourceforge.net/mailarchive/forum.php?forum_id=todo</archive>
</mailingList>
<mailingList>
<name>JMS CTS Developer List</name>
<subscribe>jms...@li...</subscribe>
<unsubscribe>jms...@li...</unsubscribe>
<archive>http://sourceforge.net/mailarchive/forum.php?forum_id=todo</archive>
</mailingList>
<mailingList>
<name>JMS CTS CVS Commits List</name>
<subscribe>jms...@li...</subscribe>
<unsubscribe>jms...@li...</unsubscribe>
<archive>http://sourceforge.net/mailarchive/forum.php?forum_id=todo</archive>
</mailingList>
</mailingLists>
<developers>
<developer>
<name>Tim Anderson</name>
<id>tima</id>
<email>tan...@us...</email>
<organization></organization>
</developer>
</developers>
<dependencies>
<dependency>
<id>adaptx</id>
<version>0.9.2</version>
<url>http://www.exolab.org/</url>
</dependency>
<dependency>
<id>ant</id>
<version>1.5.1</version>
<url>http://ant.apache.org/</url>
</dependency>
<dependency>
<groupId>ant</groupId>
<artifactId>ant-optional</artifactId>
<version>1.5.1</version>
<url>http://ant.apache.org/</url>
</dependency>
<dependency>
<id>castor</id>
<version>0.9.4.3</version>
<url>http://castor.exolab.org/</url>
</dependency>
<dependency>
<id>commons-cli</id>
<version>1.0-beta-2</version>
<url>http://jakarta.apache.org/commons/cli/</url>
</dependency>
<dependency>
<id>exolabcore</id>
<version>0.3.5</version>
<url>http://openjms.sourceforge.net/</url>
</dependency>
<dependency>
<id>jms</id>
<version>1.0.2a</version>
<url>http://java.sun.com/jms/</url>
</dependency>
<dependency>
<id>junit</id>
<version>3.7</version>
<url>http://www.junit.org/</url>
</dependency>
<dependency>
<id>log4j</id>
<version>1.1.3</version>
<url>http://jakarta.apache.org/log4j/</url>
</dependency>
<dependency>
<id>xml-apis</id>
<version>1.0.b2</version>
<url>http://xml.apache.org/xerces2-j/</url>
</dependency>
<dependency>
<id>xerces</id>
<version>2.2.1</version>
<url>http://xml.apache.org/xerces2-j/</url>
</dependency>
</dependencies>
<build>
<nagEmailAddress>jms...@li...</nagEmailAddress>
<sourceDirectory>src/java</sourceDirectory>
<unitTestSourceDirectory></unitTestSourceDirectory>
<unitTest>
<includes>
<include>**/*Test.java</include>
</includes>
</unitTest>
<resources>
<resource>
<directory>src/conf</directory>
<includes>
<include>*.xsd</include>
<include>*.dtd</include>
<include>*.mod</include>
<include>log4j.properties</include>
<include>driver.jelly</include>
<include>driver.properties</include>
</includes>
</resource>
<resource>
<directory>src/messages</directory>
<targetPath>org/apache/maven/messages</targetPath>
<includes>
<include>messages*.properties</include>
</includes>
</resource>
</resources>
</build>
</project>
|
|
From: <tan...@us...> - 2003-05-26 13:16:09
|
Update of /cvsroot/jmscts/jmscts/src/xdocs/images In directory sc8-pr-cvs1:/tmp/cvs-serv15811/src/xdocs/images Log Message: Directory /cvsroot/jmscts/jmscts/src/xdocs/images added to the repository |
|
From: <tan...@us...> - 2003-05-26 13:14:38
|
Update of /cvsroot/jmscts/jmscts/src/xdocs In directory sc8-pr-cvs1:/tmp/cvs-serv14928/src/xdocs Log Message: Directory /cvsroot/jmscts/jmscts/src/xdocs added to the repository |
|
From: <tan...@us...> - 2003-05-23 17:42:32
|
Update of /cvsroot/jmscts/jmscts/src/providers/openjms/config
In directory sc8-pr-cvs1:/tmp/cvs-serv23247
Modified Files:
openjms.xml
Log Message:
fixed provider class name
Index: openjms.xml
===================================================================
RCS file: /cvsroot/jmscts/jmscts/src/providers/openjms/config/openjms.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** openjms.xml 11 May 2003 07:51:55 -0000 1.3
--- openjms.xml 23 May 2003 17:42:29 -0000 1.4
***************
*** 1,5 ****
<?xml version="1.0"?>
<configuration>
! <proxy provider="com.intalio.jms.openjms.OpenJMSProvider"
start="true" stop="true">
<property name="Path" type="java.lang.String"
--- 1,5 ----
<?xml version="1.0"?>
<configuration>
! <proxy provider="org.exolab.jmscts.openjms.OpenJMSProvider"
start="true" stop="true">
<property name="Path" type="java.lang.String"
|
|
From: <tan...@us...> - 2003-05-23 17:40:40
|
Update of /cvsroot/jmscts/jmscts/src/bin
In directory sc8-pr-cvs1:/tmp/cvs-serv22171
Added Files:
jmscts.sh
Log Message:
added unix script to run jmscts
--- NEW FILE: jmscts.sh ---
#!/bin/sh
# -----------------------------------------------------------------------------
# Start/Stop Script for the JMS compliance test suite
#
# Required Environment Variables
#
# JAVA_HOME Points to the Java Development Kit installation.
#
# Optional Environment Variables
#
# JMSCTS_HOME Points to the JMS CTS installation directory.
#
# JAVA_OPTS Java runtime options used when the command is executed.
#
#
# $Id: jmscts.sh,v 1.1 2003/05/23 17:40:38 tanderson Exp $
# ---------------------------------------------------------------------------
# OS specific support. $var _must_ be set to either true or false.
cygwin=false
case "`uname`" in
CYGWIN*) cygwin=true;;
esac
# For Cygwin, ensure paths are in UNIX format before anything is touched
if $cygwin; then
[ -n "$JAVA_HOME" ] && JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
fi
if [ -z "$JAVA_HOME" ]; then
echo "The JAVA_HOME environment variable is not set."
echo "This is required to run jmscts"
exit 1
fi
if [ ! -r "$JAVA_HOME"/bin/java ]; then
echo "The JAVA_HOME environment variable is not set correctly."
echo "This is required to run jmscts"
exit 1
fi
_RUNJAVA="$JAVA_HOME"/bin/java
# Guess JMSCTS_HOME if it is not set
if [ -z "$JMSCTS_HOME" ]; then
# resolve links - $0 may be a softlink
PRG="$0"
while [ -h "$PRG" ]; do
ls=`ls -ld "$PRG"`
link=`expr "$ls" : '.*-> \(.*\)$'`
if expr "$link" : '.*/.*' > /dev/null; then
PRG="$link"
else
PRG=`dirname "$PRG"`/"$link"
fi
done
PRGDIR=`dirname "$PRG"`
JMSCTS_HOME=`cd "$PRGDIR/.." ; pwd`
elif [ ! -r "$JMSCTS_HOME"/bin/jmscts.sh ]; then
echo "The JMSCTS_HOME environment variable is not set correctly."
echo "This is required to run jmscts"
exit 1
fi
# Set CLASSPATH to empty by default. User jars can be added via the setenv.sh
# script
CLASSPATH=
if [ -r "$JMSCTS_HOME"/bin/setenv.sh ]; then
. "$JMSCTS_HOME"/bin/setenv.sh
fi
CLASSPATH="$CLASSPATH":"$JMSCTS_HOME"/lib/$JMSCTS$
# For Cygwin, switch paths to Windows format before running java
if $cygwin; then
JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
JMSCTS_HOME=`cygpath --path --windows "$JMSCTS_HOME"`
CLASSPATH=`cygpath --path --windows "$CLASSPATH"`
fi
POLICY_FILE="$JMSCTS_HOME"/src/etc/jmscts.policy
# Execute the requested command
echo "Using JMSCTS_HOME: $JMSCTS_HOME"
echo "Using JAVA_HOME: $JAVA_HOME"
if [ "$1" = "run" ]; then
shift
exec "$_RUNJAVA" $JAVA_OPTS -Djmscts.home="$JMSCTS_HOME" \
-classpath "$CLASSPATH" \
-Djava.security.manager -Djava.security.policy="$POLICY_FILE" \
org.exolab.jmscts.test.ComplianceTestSuite "$@"
elif [ "$1" = "stop" ] ; then
shift
"$_RUNJAVA" $JAVA_OPTS -Djmscts.home="$JMSCTS_HOME" \
-classpath "$CLASSPATH" \
-Djava.security.manager -Djava.security.policy="$POLICY_FILE" \
org.exolab.jmscts.core.Admin -stop
elif [ "$1" = "abort" ] ; then
shift
exec "$_RUNJAVA" $JAVA_OPTS -Djmscts.home="$JMSCTS_HOME" \
-classpath "$CLASSPATH" \
-Djava.security.manager -Djava.security.policy="$POLICY_FILE" \
org.exolab.jmscts.core.Admin -abort
elif [ "$1" = "snaphshot" ] ; then
shift
exec "$_RUNJAVA" $JAVA_OPTS -Djmscts.home="$JMSCTS_HOME" \
-classpath "$CLASSPATH" \
-Djava.security.manager -Djava.security.policy="$POLICY_FILE" \
org.exolab.jmscts.core.Admin -snapshot "$@"
else
echo "usage: jmscts.sh (commands)"
echo "commands:"
echo " run Start the JMS CTS"
echo " stop Stop the JMS CTS"
echo " abort Abort the JMS CTS"
echo " snapshot Take a snapshot"
exit 1
fi
|