From Berkeley The course project is : Build a consuming client application which meets the following requirements. Midterm Exam Covers lectures 1 through 6. The emphasis is on the SOAP, WSDL And UDDI standards. Specific topics included will be many of the following. All topics covered in class however are fair game. An actual exam is at Final Exam: Covers metadata repositories, WS-Security, WS-Eventing, WS-Addressing.


Helsinski asks students to write a report on a topic, and gives an extensive referenec list at Typical reports were

  1. Semantic Web Services - report by Mikko Laukkanen [Review1 -> REST ][Review2 ->Service Oriented Architecture]
  2. BPEL4WS - report by Simo Viitanen [Review1->REST ][Review2->Semantic Web Services]]
  3. XML Basics: XML, XML Schema, Namespaces - report by Aleksanteri Aaltonen - [Review1 -> SOAP & WSDL ] [Review2 -> Service Oriented Architecture]
  4. WS-Policy Framework - report by Tuomas M T Nurmela [Review1->WS-Trust][Review2->WS-Reliability]
  5. REST - report by Michael Przybilski [Review1->Semantic Web Services][Review2 ->Service Oriented Architecture]


The Chapstick shopping centre is one of Australia's largest shopping centres and hosts a large number of shops of different kinds. Chapstick already has an extensive Web site, but is contemplating moving towards an online system to support ecommerce activities.


You will need to implement a client and one or more servers using a socket-based protocol.

The client will need to be able to make the following requests to the Chapstick central server:

Pass level

A client talking to a single server. The server handles all of the Chapstick requests. The server keeps lists of the shops, of their types and has a catalogue for each shop. All of this can be done using local files and/or lists and tables kept in memory.

This level demonstrates that you can specify a protocol for communication between a client and a single server and implement this protocol in a simple way.

Extra level

The specification given above will gain a Pass grade if done satisfactorily. Higher grades will be given on completion of additional functionality. Each additional function will gain an extra grade (to a maximum of HD). The additional functions are

All databases are managed by a database system such as Access, Oracle or MySQL. The server communicates with the database by JDBC calls.
This level shows that you can manage a typical 3-tier system with presentation, logic and database handled separately.
Multiple servers
Each shop runs its own server. Chapstick will forward certain requests (such as catalogue) directly to the shop's server rather than maintaining information on its own server.
This level demonstrates that you can deal with a multi-tier system with many servers at the backend
All sensitive accesses are performed using security mechanisms, such as encryption and validation. Each server should be able to validate its identity using certificates
This level shows that you can handle the authorisation, security and privacy issues that can arise
Web access
Web access to the Chapstick service should be made available. This will mean a CGI script/Java servlet/etc that can act as a client to the Chapstick server. This will involve a set of Web pages and HTTP backends to handle form requests.
This is in addition to an ordinary client, not as a replacement
This level will add alternative access mechanisms to the service, which makes it Web-accessible to humans

Jan Newmarch (
Last modified: Mon Dec 5 11:23:19 EST 2005
Copyright ©Jan Newmarch
Access count since May 2005 is:
This page is