JAX-WS Dispatch/Provider Demo 
=============================

The demo demonstrates the use of JAX-WS Dispatch and Provider interface.
The client side Dispatch instance invokes upon an endpoint using a JAX-WS 
Provider implementor. There are three different invocations from the client. 
The first uses the SOAPMessage data in MESSAGE mode. The second uses the DOMSource 
data in MESSAGE mode. The third uses the DOMSource in PAYLOAD mode. The three 
different messages are constructed by reading in the XML files found in the 
src/demo/hwDispatch/client directory.

Please review the README in the samples directory before
continuing.

Building and running the demo using Maven
---------------------------------------
From the base directory of this sample (i.e., where this README file is
located), the pom.xml file is used to build and run the demo. 

Using either UNIX or Windows:

  mvn install   (builds the demo)
  mvn -Pserver  (from one command line window)
  mvn -Pclient  (from a second command line window)


To remove the code generated from the WSDL file and the .class
files, run "mvn clean".



Building the demo using wsdl2java and javac
-------------------------------------------
If your environment already includes cxf-manifest.jar on the
CLASSPATH, and the JDK directory on the PATH
it is not necessary to set the environment as described in
the samples directory's README.  If your environment is not
properly configured, or if you are planning on using wsdl2java,
javac, and java to build and run the demos, you must set the
environment.

From the base directory of this sample (i.e., where this README file is
located) first create the target directory build/classes and then 
generate code from the WSDL file.


For UNIX:
  mkdir -p build/classes

  wsdl2java -d build/classes -compile ./wsdl/hello_world.wsdl

For Windows:
  mkdir build\classes
    Must use back slashes.

  wsdl2java -d build\classes -compile .\wsdl\hello_world.wsdl
    May use either forward or back slashes.

Now compile the provided client and server applications with the commands:

For UNIX:  
  
  export CLASSPATH=$CLASSPATH:$CXF_HOME/lib/cxf-manifest.jar:./build/classes
  javac -d build/classes src/demo/hwDispatch/client/*.java
  javac -d build/classes src/demo/hwDispatch/server/*.java

For Windows:
  set classpath=%classpath%;%CXF_HOME%\lib\cxf-manifest.jar;.\build\classes
  javac -d build\classes src\demo\hwDispatch\client\*.java
  javac -d build\classes src\demo\hwDispatch\server\*.java
  
Finally, copy resource files into the build/classes directory with the commands:

For UNIX:    
  cp ./src/demo/hwDispatch/client/*.xml ./build/classes/demo/hwDispatch/client
  cp ./src/demo/hwDispatch/server/*.xml ./build/classes/demo/hwDispatch/server

For Windows:
  copy src\demo\hwDispatch\client\*.xml build\classes\demo\hwDispatch\client
  copy src\demo\hwDispatch\server\*.xml build\classes\demo\hwDispatch\server


Running the demo using java
---------------------------

From the base directory of this sample (i.e., where this README file is
located) run the commands, entered on a single command line:

For UNIX (must use forward slashes):
    java -Djava.util.logging.config.file=$CXF_HOME/etc/logging.properties
         demo.hwDispatch.server.Server &

    java -Djava.util.logging.config.file=$CXF_HOME/etc/logging.properties
         demo.hwDispatch.client.Client ./wsdl/hello_world.wsdl

The server process starts in the background.  After running the client,
use the kill command to terminate the server process.

For Windows (may use either forward or back slashes):
  start 
    java -Djava.util.logging.config.file=%CXF_HOME%\etc\logging.properties
         demo.hwDispatch.server.Server

    java -Djava.util.logging.config.file=%CXF_HOME%\etc\logging.properties
       demo.hwDispatch.client.Client .\wsdl\hello_world.wsdl

A new command windows opens for the server process.  After running the
client, terminate the server process by issuing Ctrl-C in its command window.


