The different parts are:
The controller servlet. This servlet represents the controller in the MVC design pattern and provides a single point of entry for all requests.
The Command Chain. A tool that defines an API for workflow control.
The Editor. A tool that defines an API for generating HTML-forms.
A set of taglibs. These taglibs conforms with some of the commonly used metadata vocabularies.
The SCAM Controller represents the controller in the MVC design pattern. It is designed according to the J2EE Front Controller design pattern and provides a single point of entry for all requests. The SCAM Controller provides a framework for developing and configuring a set of reusable operations. The SCAM Controller is independent of the back-end implementation, it provides an interface for accessing different data repositories. Currently this framework is incorporated in the HTTP-proxy, which represents the view in the MVC design pattern.
The framework consists of a Command Chain Configuration, a set of Command objects and a Meta Repository Factory. The HTTP-proxy is an reference implementation and includes a Controller Servlet, a Tag library, a set of value helpers (Java Beans) and a set Java Server Pages.