Handbuch ESR

The procedure is logged in the cmd window and takes a few seconds. The generated source files, the
compiled classes and the complete jar are now available in the Build directory. The jar file must be now be
referenced when implementing the client program on the classpath. A whole lot of jar files have to be
included in the class path in order to be able to compile and execute the client program. These are listed
below.
• jwsdp-shared
jaxp
jaxrpc
saaj
xws-security
lib
lib
lib
lib
lib
activation.jar
jax-qname.jar
mail.jar
endorsed
jaxp-api.jar
jaxrpc-impl.jar
jaxrpc-spi.jar
jaxrpc-api.jar
saaj-impl.jar
saaj-api.jar
security-plugin.jar
soapprocessor.jar
xmlsec.jar
xws-security_jaxrpc.jar
xws-security.jar
dom.jar
xercesImpl.jar
xalan.jar
Now for the implementation of the client. Our example here will show the retrieval of the list of open
bills, i.e. the biller’s view. This person must have a valid username and password. If possible, these should
be stored in a separate file or database and must on no account be accessible to unauthorized persons.
First, there is an initialization block. In this example, the URLs of the web service and the eBillAccountID
are stored in a properties file and read in via a property object. However, you can decide about this
yourself. The important thing is to initialize the stub class and set the ENDPOINT_ADDRESS_PROPERTY.
String serviceURL = pApplication.getProperty("ServiceUrl");
DownloadInvoiceSoap_Stub stub =
(DownloadInvoiceSoap_Stub)(dwnlService.getDownloadInvoiceSoap());
stub._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY, serviceURL);
String eBillAccountID = pApplication.getProperty("eBillAccountID");
Next, you can already call up the method itself, because the proxy classes add the WS-Security extensions
here (see Fig 3).
ArrayOfReport report = stub.getOpenList(eBillAccountID);
16/19