Jargus had to offer two key features: an extensible set of validations and a customizable output format. Both
requirements where obvious as not all kinds of needed validation can be implemented or even known
by framework developers. The latter feature was necessary as every application needs its appropriate
output format.
The design of Jargus was driven by two design patterns: Command and Observer, these are introduced in [1].
Jargus utilizes the Command pattern to perform the actual validation. All validation tasks are propagated to these classes using Validation class. If you want to perform a validation you have to implement theValidator interface. Observer pattern is used to enable application developers to implement their custom output formats, where classes implementing ValidationHandler interface are notified about validation results, in publish and subscribe manner. The picture below depicts Jargus in UML syntax.
UML Diagram of validation framework. Created using TogetherJ Whiteboard Edition.
Click to enlarge.
