nmukhi 2002/12/27 12:47:22
Modified: java/samples/jms/client/dynamic README.html
java/samples/jms/client/stub README.html
Added: java/samples/jms/client/jboss_setup jboss.bat
Log:
Added script to set up client classpath to run JMS sample in JBoss environment.
Added info to client README files as well.
Revision Changes Path
1.2 +2 -1 xml-axis-wsif/java/samples/jms/client/dynamic/README.html
Index: README.html
===================================================================
RCS file: /home/cvs/xml-axis-wsif/java/samples/jms/client/dynamic/README.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- README.html 27 Dec 2002 17:52:07 -0000 1.1
+++ README.html 27 Dec 2002 20:47:21 -0000 1.2
@@ -10,7 +10,8 @@
<h2>
Web Services Invocation Framework:<br>
Invoking the JMS Sample using WSIF's dynamic invocation interface</h2>
-<p>After you have <a href="../../../../doc/samples.html">set up the CLASSPATH in
your environment</a>, to invoke this sample using WSIF's DII, run the DynamicInvoker
class. Specify as command line arguments the location of the WSDL file for the jms
sample followed by the operation you wish to invoke and the zip code you are
interested in. For example, <br><tt>java clients.DynamicInvoker
samples/jms/ServiceAvailability.wsdl checkAvailability 10050</tt></p>
+<p>First you need to <a href="../../../../doc/samples.html">set up the CLASSPATH in
your environment</a>. Beyond the standard classpath setting, you also need to add the
J2EE client jar files to your classpath. The set of J2EE client JARs is vendor
specific; refer to the documentation in your application server on how to set up the
environment for an EJB client, and add the JAR files specified. For JBoss users, we
have included a script to set up the client environment. To run this script, make sure
you are in your base WSIF directory (the one that contains the <tt>classpath.bat</tt>
script. Set the variable <tt>JBOSS_HOME</tt> to point to your JBoss installation. From
there, run the command <tt>samples\ejb\client\jboss_setup\jboss.bat</tt>. This sets up
the entire client classpath required to run the sample using JBoss client JAR
files.</p>
+<p>To invoke this sample using WSIF's DII, run the DynamicInvoker class. Specify as
command line arguments the location of the WSDL file for the jms sample followed by
the operation you wish to invoke and the zip code you are interested in. For example,
<br><tt>java clients.DynamicInvoker samples/jms/ServiceAvailability.wsdl
checkAvailability 10050</tt></p>
<p>To see details of how the WSIF API is used to make invocations dynamically, take
a look at the code for the <a
href="../../../clients/DynamicInvoker.java">DynamicInvoker class</a>.</p>
<hr width="100%">
</body></html>
1.1 xml-axis-wsif/java/samples/jms/client/jboss_setup/jboss.bat
Index: jboss.bat
===================================================================
@echo off
REM Written by Nirmal Mukhi and Alek Slominski
REM Purpose of script: add JBoss client JARs to the classpath
REM so that WSIF EJB sample can be run using JBoss J2EE client jars
REM check for JBoss home
if "%JBOSS_HOME%" == "" goto jbosshomeerror
set JBOSS_HOME=%JBOSS_HOME%
REM setup classpath to run WSIF sample using JBoss EJB client JARs
call classpath.bat quiet
REM add to JBOss client JARs to classpath
for %%i in (%JBOSS_HOME%\client\*.jar) do call lib\ant\lcp.bat %%i
REM set the classpath
set CLASSPATH=%LOCALCLASSPATH%
echo %CLASSPATH%
goto end
:jbosshomeerror
echo "ERROR: JBOSS_HOME not found in your environment."
echo "Please, set the JBOSS_HOME variable in your environment to match the"
echo "location of your JBoss installation."
:end
1.2 +1 -1 xml-axis-wsif/java/samples/jms/client/stub/README.html
Index: README.html
===================================================================
RCS file: /home/cvs/xml-axis-wsif/java/samples/jms/client/stub/README.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- README.html 27 Dec 2002 17:52:07 -0000 1.1
+++ README.html 27 Dec 2002 20:47:22 -0000 1.2
@@ -10,7 +10,7 @@
<h2>
Web Services Invocation Framework:<br>
Invoking the JMS Sample through a high level stub interface</h2>
-First, you must <a href="../../../../doc/samples.html">set up the CLASSPATH in your
environment</a>.
+<p>First you need to <a href="../../../../doc/samples.html">set up the CLASSPATH in
your environment</a>. Beyond the standard classpath setting, you also need to add the
J2EE client jar files to your classpath. The set of J2EE client JARs is vendor
specific; refer to the documentation in your application server on how to set up the
environment for an EJB client, and add the JAR files specified. For JBoss users, we
have included a script to set up the client environment. To run this script, make sure
you are in your base WSIF directory (the one that contains the <tt>classpath.bat</tt>
script. Set the variable <tt>JBOSS_HOME</tt> to point to your JBoss installation. From
there, run the command <tt>samples\ejb\client\jboss_setup\jboss.bat</tt>. This sets up
the entire client classpath required to run the sample using JBoss client JAR
files.</p>
<p>This directory contains a file called <tt>Run.java</tt> that contains the
<tt>main</tt> method. This is the logic that uses the generated stub interface to run
the sample. So you can run this class, specifying on the command line the location of
the WSDL file for the sample and the zip code you are interested in. For example, <br>
<tt>java jms.client.stub.Run samples/jms/ServiceAvailability.wsdl 10050</tt></p>
<p>To generate the stub interface, you can use any tool that generates Java
interfaces for WSDL services using their port type descriptions. WSDL2Java, which is
packaged with Axis, unfortunately does not work since the presence of a JMS binding in
the WSDL confuses it, so we actually wrote our stub interface by hand. It is available
<a href="org/apache/xml/CheckAvailabilityPortType.java">here</a>. Note that WSIF
assumes a correspondence between the generated Java interface and the WSDL port type
that has its abstract description as specified in the JAX-RPC specification.<br>
