Difference between revisions of "CodelistManagerDesign"
(→WebFragment) |
(→Architecture) |
||
| Line 6: | Line 6: | ||
=Architecture= | =Architecture= | ||
[[File:CMArchitecture.png]] | [[File:CMArchitecture.png]] | ||
| + | |||
| + | The core defines a basic user interface, the core services, core daos and the core domain objects. The core implements the core usecases. | ||
| + | |||
| + | Every module covers 1 or more use cases. A module has usually a lot of UI definitions, and may add services, daos and domain objects. | ||
=Package Diagram= | =Package Diagram= | ||
Revision as of 16:53, 16 April 2012
Context
Architecture
The core defines a basic user interface, the core services, core daos and the core domain objects. The core implements the core usecases.
Every module covers 1 or more use cases. A module has usually a lot of UI definitions, and may add services, daos and domain objects.
Package Diagram
Dozer is a utility to define mappings between object graphs.
Module Architecture
An instance of a CodelistManager can be deployed on a Java application server. A module can be packaged in a Custom, Porlet of WebFragment way.
Proprietary
The CodelistManager will have its own definitions of the notion of a module. Geoserver has done something similair. Every module is a jar file, can be dropped on the classpath and will add definitions to the UI menu. Geoserver has used intensively the Spring framework in order to implement its modularity.
Portlet
Packaging as portlet means complying with the Java Portlet Specification 2.0 (JSR 286). The portlets can be deployed on a portal server like [1].
WebFragment
Servlet 3.0 introduces web fragments. Every module can be packaged as a webfragement. http://java.sun.com/developer/technicalArticles/JavaEE/JavaEE6Overview_Part2.html
