Package uk.ac.sheffield.vtts.client.ws

This package contains skeleton JAX-WS Java clients for testing with generated JUnit test drivers that test JAX-WS Java clients for SOAP services.

See: Description

Interface Summary

Interface	Description
DocumentStoreInterface	DocumentStoreInterface is a skeleton of the JAX-WS client interface for the JAX-WS implementation of the DocumentStore.xml example.
ShoppingCartInterface	ShoppingCartInterface is a skeleton of the JAX-WS client interface for the JAX-WS implementation of the ShoppingCart.xml example.

Class Summary

Class	Description
Document	Document is an example witness-type, implementing the symbolic type used in the DocumentStore.xml specification.
DocumentStoreService	DocumentStoreService is a skeleton of the JAX-WS resource class needed for the JAX-WS implementation of the DocumentStore.xml example.
Dvd	Dvd is an example witness-type, implementing the symbolic type used in the ShoppingCart.xml specification.
ShoppingCartService	ShoppingCartService is a skeleton of the JAX-WS resource class needed for the JAX-WS implementation of the ShoppingCart.xml example.

Exception Summary

Exception	Description
BadDocumentIdentifier	BadDocumentIdentifier is a kind of RuntimeException thrown by the example service DocumentStore.
BadVersionIdentifier	BadVersionIdentifier is a kind of RuntimeException thrown by the example service DocumentStore.

Package uk.ac.sheffield.vtts.client.ws Description

This package contains skeleton JAX-WS Java clients for testing with generated JUnit test drivers that test JAX-WS Java clients for SOAP services. It is part of the Broker@Cloud Verification and Testing Tool Suite, v1.0, © Anthony J H Simons and Raluca Lefticaru, 2015. Main web site: http://staffwww.dcs.shef.ac.uk/people/A.Simons/broker/.

Sub-package uk.ac.sheffield.vtts.client.ws

This package is a repository where you may place service clients that are JAX-WS Java clients for a SOAP and WSDL service. Target JAX-WS-testers onto clients in this package. We have only sketched the outlines of the two kinds of client object (a resource class; and an interface) with which generated test-drivers expect to interact; since you will need to create the web clients yourself, using the tools offered by the JAX-WS development framework.

In general, you will use the JAX-WS development framework to build your JAX-WS web service. The service implementation may have been created bottom-up starting with the annotated Java service, from which the WSDL was generated (using JAX-WS wsgen); or top-down starting with the WSDL and generating the service resource classes (using JAX-WS wsimport). We then assume that a Java client is created from the WSDL (using JAX-WS wsdl2java). This creates two entities, a client implementation and a service interface, against which all service calls are made. The names of the interface methods must match the names used in the original service specification.

Apart from the service clients, further kinds of domain object (such as the class DVD used in the ShoppingCart example) are provided here, so that they are available to the generated test-drivers along with the tested service client.