You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by nm...@apache.org on 2003/01/22 22:00:53 UTC
cvs commit: xml-axis-wsif/java/samples/multibinding/client/dynamic README.html
nmukhi 2003/01/22 13:00:53
Modified: java/samples/complexsoap/client/dynamic README.html
java/samples/ejb/client/jboss_setup jboss.bat
java/samples/jms/client/jboss_setup jboss.bat
java/samples/jms/service README.html
java/samples/jms/service/deploy/jboss
serviceavailability.jar
java/samples/multibinding/client/dynamic README.html
Log:
Minor changes to docs, scripts; rebuilt JAR file for easy deployment
of JMS (previous version of JAR file had old version of class)
Revision Changes Path
1.5 +1 -1 xml-axis-wsif/java/samples/complexsoap/client/dynamic/README.html
Index: README.html
===================================================================
RCS file: /home/cvs/xml-axis-wsif/java/samples/complexsoap/client/dynamic/README.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- README.html 20 Dec 2002 17:38:41 -0000 1.4
+++ README.html 22 Jan 2003 21:00:52 -0000 1.5
@@ -9,7 +9,7 @@
<h2>
Web Services Invocation Framework:<br>
-Invoking the SimpleSOAP Sample using WSIF's dynamic invocation interface</h2>
+Invoking the ComplexSOAP 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 <tt>Run</tt> class located in this directory. Specify as command line arguments the location of the WSDL file for the service and the zip code you are interested in. For example, <br><tt>java complexsoap.client.dynamic.Run samples/complexsoap/Zip2Geo.wsdl 10005</tt></p>
<p>Look at the code in the <tt>Run.java</tt> file in this directory to see how to use WSIF's DII yourself. Note that the <tt>DynamicInvoker</tt> class we used to <a href="../../../simplesoap/client/dynamic/README.html">invoke the simplesoap sample dynamically</a> cannot be used for this one since the <tt>DynamicInvoker</tt> as it stands now is limited to invocation of services using primitive schema types only.</p>
<hr width="100%">
1.2 +1 -1 xml-axis-wsif/java/samples/ejb/client/jboss_setup/jboss.bat
Index: jboss.bat
===================================================================
RCS file: /home/cvs/xml-axis-wsif/java/samples/ejb/client/jboss_setup/jboss.bat,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- jboss.bat 13 Dec 2002 22:59:55 -0000 1.1
+++ jboss.bat 22 Jan 2003 21:00:53 -0000 1.2
@@ -12,7 +12,7 @@
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
+for %%i in (%JBOSS_HOME%\client\*.jar) do call lcp.bat %%i
REM set the classpath
set CLASSPATH=%LOCALCLASSPATH%
1.2 +1 -1 xml-axis-wsif/java/samples/jms/client/jboss_setup/jboss.bat
Index: jboss.bat
===================================================================
RCS file: /home/cvs/xml-axis-wsif/java/samples/jms/client/jboss_setup/jboss.bat,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- jboss.bat 27 Dec 2002 20:47:22 -0000 1.1
+++ jboss.bat 22 Jan 2003 21:00:53 -0000 1.2
@@ -12,7 +12,7 @@
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
+for %%i in (%JBOSS_HOME%\client\*.jar) do call lcp.bat %%i
REM set the classpath
set CLASSPATH=%LOCALCLASSPATH%
1.3 +1 -1 xml-axis-wsif/java/samples/jms/service/README.html
Index: README.html
===================================================================
RCS file: /home/cvs/xml-axis-wsif/java/samples/jms/service/README.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- README.html 16 Jan 2003 18:07:28 -0000 1.2
+++ README.html 22 Jan 2003 21:00:53 -0000 1.3
@@ -11,7 +11,7 @@
Web Services Invocation Framework:<br>
Implementing the JMS service</h1>
<p>The JMS service is implemented as a message driven bean (MDB). In case you need to learn more about MDBs, you can refer to various guides and tutorials available for free online; I found <a href="http://www.onjava.com/pub/a/onjava/excerpt/ejb3_ch13/index.html">this excerpt from Richard Monson-Haefel's EJB book</a> useful.</p>
-<p>The bean implementation is very simple. It acts as a message listener (the queue is determined by the deployment files). When a message is delivered, it extracts the body (recall that we are using JMSTextMessages to communicate back and forth since we are just exchanging strings). This is presumably a valid zip code, so the bean makes it an integer in an unsafe and intrepid manner. Here is applies some logic to determine whether DSL service is available at this zip code or not. A real-world implementation would invariably refer to some backend database using JDBC or do something similarly smart. Our implementation, being just a sample, returns true for all zip codes < 5000, and false otherwise. The return message is sent to the queue specified in the <tt>replyTo</tt> field of the request message. Note that the bean must encode the correct <tt>JMSCorrelationID</tt> in the return message in order for it to be picked up by WSIF. <a href="ServiceAvailabilityBean.java">Here</a> is the code for our MDB.</p>
+<p>The bean implementation is very simple. It acts as a message listener (the queue is determined by the deployment files). When a message is delivered, it extracts the body (recall that we are using JMSTextMessages to communicate back and forth since we are just exchanging strings). This is presumably a valid zip code, so the bean makes it an integer in an unsafe and intrepid manner. Here is applies some logic to determine whether DSL service is available at this zip code or not. A real-world implementation would invariably refer to some backend database using JDBC or do something similarly smart. Our implementation, being just a sample, returns true for all zip codes < 50000, and false otherwise. The return message is sent to the queue specified in the <tt>replyTo</tt> field of the request message. Note that the bean must encode the correct <tt>JMSCorrelationID</tt> in the return message in order for it to be picked up by WSIF. <a href="ServiceAvailabilityBean.java">Here</a> is the code for our MDB.</p>
<p>The <tt><a href="deploy">deploy</a></tt> subdirectory contains the things necessary to deploy this MDB to your favorite application server. Generally to deploy your MDB you will need to compile the code for this sample, then package it into a JAR along with the <tt><a href="deploy/jboss/ejb-jar.xml">ejb-jar.xml</a></tt> file. Your application server may need other files, take a look at app server specific instructions under the deploy directory. You will also need to fill in the vendor specific deployment information in the sevice WSDL, instructions for which you will also find under the deploy directory.
<hr width="100%">
</body></html>
1.2 +8 -12 xml-axis-wsif/java/samples/jms/service/deploy/jboss/serviceavailability.jar
<<Binary file>>
1.3 +0 -1 xml-axis-wsif/java/samples/multibinding/client/dynamic/README.html
Index: README.html
===================================================================
RCS file: /home/cvs/xml-axis-wsif/java/samples/multibinding/client/dynamic/README.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- README.html 7 Jan 2003 17:52:43 -0000 1.2
+++ README.html 22 Jan 2003 21:00:53 -0000 1.3
@@ -19,4 +19,3 @@
<hr width="100%">
</body></html>
-WRONG FILE
\ No newline at end of file