-
Notifications
You must be signed in to change notification settings - Fork 5
Architecture (TBC)
Patrick Moawad edited this page Feb 24, 2016
·
4 revisions
The ValidationFramework currently provides the following Maven artifacts:
- validationframework-core: this artifact is the basic layer that contains all the basic APIs and basic implementations that do not depend on a particular UI component library or other specific usage. Every project using the ValidationFramework should depend and use this artifact.
- validationframework-swing: this artifact is a layer built on top of the core and provides support of AWT/Swing by providing a specific implementation of triggers, data providers, rules, result handlers and properties. Default sets of triggers based on components events (model change, focus loss, etc.), data providers retrieving the data from the components (model value, input text, etc.), rules depending on component formatters, result handlers based on component decorations, and properties representing component bean properties are provided.
- validationframework-javafx: this artifact is a layer built on top of the core and provides support of JavaFX by providing a specific implementation of triggers, data providers, rules and result handlers.
- validationframework-experimental: this artifact contains some experimental implementations and utility classes that may one day be part of the validationframework-core, validationframework-swing or validationframework-javafx artifacts. The classes of this artifact are not yet stable and their use is discouraged, unless you know what you are doing.
- validationframework-demo: this artifact contains example pieces of code.
- validationframework-itest-osgi: this artifact contains some tests for the integration of the framework in OSGi.
Other artifacts will be added in the future, for instance, a layer to support components from the JIDE and SwingX libraries, SWT, GWT, etc.
- validationframework.api: Package containing all the base interfaces used and proposed by the framework. These interfaces are used to define triggers, data providers, rules, result handlers and basic validators connecting everything together.
- validationframework.base: Package containing some base implementations of the interfaces from the api package. Abstract implementations, default simple rules validating string input, boolean results manipulation, etc. are examples of package contents.
- validationframework.swing: Packaging containing implementations related to AWT/Swing. Triggers based on Swing components, data providers retrieving the data from component models, result handlers based on component decoration, etc., are examples of package contents.
- validationframework.javafx: Packaging containing implements related to JavaFX. Triggers based on properties and observable objects, data providers retrieving the value of properties, result handlers decorating nodes, etc., are examples of package contents.
Please refer to the Javadoc for further package decomposition and documentation.
TBC...
TBC...
TBC...