Difference between revisions of "Vox"
From D4Science Wiki
| Line 1: | Line 1: | ||
| + | [[Cotrix configuration and deployment scenarios]] | ||
| + | |||
== Component diagram == | == Component diagram == | ||
This is a diagram where high-level components are identified, including their ''dependencies''. | This is a diagram where high-level components are identified, including their ''dependencies''. | ||
Latest revision as of 18:07, 5 December 2012
Cotrix configuration and deployment scenarios
Component diagram
This is a diagram where high-level components are identified, including their dependencies.
Note that vox-services has not been split in platform and core. It probably should.
Platform
Platform is referred to as web application platform. It does not have any functional components. It implements non functional requirements as:
- authentication
- authorisation
- menu CodelistManagerDesign#Publish_.26_Subscribe_for_the_Menu
- workflow
- plugin architecture
- OSGI
Core
Core implements functions specific to the domain. The component vocbench-core implements vocabulary management. The component cotrix-core implements codelist management.
Vox
Vox is everything what VocBench and Cotrix have in common and share.
Service
A service is either a GWT or a REST webservice.
