From Bodington Wiki

Jump to: navigation, search

Back to TReCX



The one below is hopefully clearer and it should more accurately reflect the current architecture. Therefore, it may change over time.


UML2 Component Diagram

This is an implementation diagram of the architecture implemented using the nomenclature of a UML2 component diagram. The interfaces are shown using the ball-and-socket notation of provided (the end attached to the ball) and required (the end attached to the socket) interfaces (note: the diagramming tool decided to remove the ball glyph once I attached the "required" end!). The applications are shown as "components" in the sense that these can (in principle) be swapped in and out. It is intended to highlight the importance of the interfaces and the fact that a reporting application can only query applications which contain tracking stores.


The diagram was drawn using MagicDraw.

Design guidelines

JISC recommended that we:

  • use document literal web service calls, we could use CASTOR, xmlbeans and AXIS to convert from XML to 'program objects'.
  • ensure that the WSDL represents 'business process' and not software operations.

However, we would like to move away from SOAP and AXIS and use a RESTian approach if possible. Possibly, but I think what with the developer convenience of Java 5 annotations I personally think it's worth having a a stab at SOAP "proper" ;-).

WSDLs for REST services

Back to TReCX