Skip to content
bgoldowsky edited this page Aug 23, 2016 · 10 revisions

This diagram shows the dependencies between the various modules and selected dependencies on third-party libraries.

Block diagram of the CWM modules and their dependencies

The orange boxes are the modules that are included in this project. From the bottom up:

  • cwm-base: lightweight dependency containing basic interfaces, Guice dependency injection setup, and some unit testing infrastructure.
  • cwm-components: miscellaneous useful wicket components.
  • cwm-xml: use transformed XML content on web pages.
  • cwm-glossary: use an XML file as a glossary; link glossary words to their definitions.
  • cwm-dav: use content stored on a WebDAV server
  • cwm-figuration: connect Figuration framework to Wicket
  • cwm-db: connect Hibernate to Wicket, with detachable models, open-session-in-view, etc.
  • cwm-search: connect Hibernate Search to Wicket, allowing full-text search over database objects.
  • cwm-data: common database classes for and components to manage them
  • cwm-tag: support for tagging, built on top of the cwm-data structures

The blue box has its own Github project:

  • cwm-drawtool: Javascript drawing tool integrated into Wicket

The white boxes are third party dependencies (not exhaustively listed, just the most significant ones).

Not shown are several deprecated modules:

  • cwm-mediaplayer: use the JW Player for video and audio (removed in wicket-7 branch)
  • cwm-audioapplet: Java/Javascript audio recorder for web pages (removed in wicket-7 branch)
  • cwm-wami: connects the WAMI Javascript/Flash audio recorder to wicket (removed in wicket-7 branch)

Clone this wiki locally