Handbuch ESR

More documents

Recommendations

Info

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
There is another configuration file called user-pass-authenticate-client.xml. This file contains all the information necessary to ensure that the WS-Security extensions are included when generating the proxy classes. Yellowworld.WSSecurirty.ClientSecurityEnvironmentHandler Fig 3: Contents of user-pass-authenticate-client.xml This configuration file defines that the SOAP request must contain a username token and a timestamp (as per WS-Security specification ht tp://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf and ht tp://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf). The framework automatically inserts this XML node at runtime. You do not have to do this. The only thing you may have to change here is the class name of the callback handler. In our case this is the ClientSecurityEnvironmentHandler. In this class you can define how you wish to read in the username and password, e.g. from a file, from a database, etc. Once you have made all the necessary changes, you can start generating the proxy classes with the ant tool. To do this, enter the following command on the command line: ant –f webserviceclient.xml 15/19
Page 1 and 2: E-bill Instruction for a client imp
Page 3 and 4: 1. Introduction Within the e-bill p
Page 5 and 6: A NotProcessedInvoice entry indicat
Page 7 and 8: public class ProtocolReport { publi
Page 9 and 10: 3.2.1.2 GetInvoiceByID This method
Page 11 and 12: 4. Implementation This section serv
Page 13: Because the web service is located
Page 17 and 18: Next, there is a simple evaluation
Page 19: Annex A Links relating to the integ

Handbuch ESR

Create successful ePaper yourself

Delete template?

Save as template?