First you need to set up the CLASSPATH in your environment. 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. We have included below instructions for some app servers, follow that link if you happen to be using one of those, otherwise refer to the documentation in your application server on how to set up the environment for a JMS client.
Setting up the client on some app servers
Running the client
This directory contains a file called Run.java that contains the main 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,
java jms.client.stub.Run samples/jms/ServiceAvailability.wsdl 10050
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 here. 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.