Handbuch ESR

4.3 Implementation in Java
As already mentioned, we will discuss only the JWSDP 1.5 framework. The preparations described in
section 2.2 must have been completed. Here, too, the first step is to generate the proxy classes. The Sun
documentation is usually based on the assumption that one wants to publish a web service and therefore
they require the installation of a web container such as Tomcat. In our case, we really only need the client
and there is thus no need for an application server or web container.
The generation of client proxy classes using WS-Security extensions is not well documented. Therefore, we
recommend that you take the enclosed configuration files and edit them.
First of all, the webserviceclient.props file has to be edited. Values must be assigned to all parameters
except the proxy information. The meanings of the individual parameters can be taken from the
comments in Fig 1.
# place where Java is installed
javahome=C:/Java/2sdk1.4.2_07
# place where JWSDP is installed
jwsdp.home=C:/Java/jwsdp-1.5
# Destination of the generated classes
build.dir=build
# Destination of generated jar File
dist.dir=dist
# Location of the Configuration-File
configfile=config/client-config.xml
# Proxy Server Host if there is one
proxy.host=
# Proxy Server Port if there is a Proxy Server
proxy.port=
# Name of the jar File
jarname=DownloadInvoiceProxy
# Set to true or false to control jaxrpc tool output
jaxrpc.tool.verbose=true
Fig 1: Contents of the webserviceclient.props file
The webserviceclient.xml file is a control file for the ant tool which is included in the JWSDP package. It is
located in \apache-ant\bin. The XML file references the configuration above, assembles
the class path, contains compiler instructions for generating classes and much more. In our case, nothing
has to be changed in this file. We still recommend, however, that you have a look at it in order to
understand the procedure.
Next, the client-config.xml file has to be edited. Here you have to enter the URL of the WSDL file and the
name of the package to be generated.
Fig 2: Contents of the client-config.xml file
14/19