dOOv alternatives and similar libraries
Based on the "Bean Mapping" category.
Alternatively, view dOOv alternatives based on common mentions on social networks and blogs.
Do you think we are missing an alternative of dOOv or a related project?
Popular Comparisons
README
dOOv (Domain Object Oriented Validation)
dOOv is a fluent API for typesafe domain model validation and mapping. It uses annotations, code generation and a type safe DSL to make domain model validation and mapping fast and easy.
[dOOv logo](docs/svg/doov_logo_2020_blue.svg)
Documentation
See the getting started section in the wiki, or see the small usage overview.
Example
See the [the sample project in dOOv](sample). It contains two model domains, maven and gradle code generation, and example rules.
Conferences
See our presentation slides at JDK.IO.
See our presentation slides at Oracle Code One.
See our presentation slides about the implementation of failure cause at Sorbonne University.
See our presentation slides latest update done at Oracle Code Rome.
Usage
Overview
Annotate your model with @Path annotations on field, qualifying them with field ids (see wiki section Domain Model Annotation)
public class User {
@SamplePath(field = SampleFieldId.FIRST_NAME, readable = "user first name")
private String firstName;
@SamplePath(field = SampleFieldId.LAST_NAME, readable = "user last name")
private String lastName;
@SamplePath(field = SampleFieldId.BIRTHDATE, readable = "user birthdate")
private LocalDate birthDate;
}
Use the dOOv code generator to generate a DSL with elements userFirstName
, userLastName
and userBirthDate
(see wiki section DSL Code Generation).
Validation
Then write your rules with entry point DOOV#when
and terminal operation ValidationRule#validate
(see wiki section Validation Rules).
ValidationRule rule = DOOV.when(userBirthdate.ageAt(today()).greaterOrEquals(18))
.validate();
You can create more complex rules by chaining and
and or
or by using matching methods from the DOOV
class like matchAny
, etc.
DOOV.when(userBirthdate.ageAt(today()).greaterOrEquals(18)
.and(userFullName.isNotNull()))
.validate()
You can then execute the rule on an instantiated model (see wiki section Validation Engine).
// Execute the DSL on the model
DslModel model = new SampleModelWrapper(sampleModel);
Result result = rule.executeOn(model);
if (result.isFalse()) {
// do stuff on the model that didn't validate
}
The result will return true or false depending on the result of the predicate, for example Result#isTrue
means the predicate validated.
Mapping
Use DOOV#map
to write mapping code using the DSL.
MappingRegistry mappings = mappings(
map(userFirstName, userLastName)
.using(biConverter((first, last) -> first + " " + last))
.to(accountFullName),
map(userBirthdate)
.using(date -> Years.yearsBetween(date, LocalDate.now()))
.to(accountAge));
You can then execute the mapping code on two instantiated models.
DslModel model1 = new SampleModelWrapper(sampleModel1);
DslModel model2 = new SampleModelWrapper(sampleModel2);
Context context = mappings.executeOn(model1, model2);
// do stuff with model2 new values
Syntax tree
The rules provides an AST that can be printed as a human readable format with the Readable#readable
method that is available on any DSL object. By default the output is from AstLineVisitor
that outputs the string in plain text (see wiki section Validation Engine).
DOOV.when(userBirthdate.ageAt(today()).greaterOrEquals(18)).validate().readable()
> When user age at 'today' greater or equals '18', validate with empty message
Testing
Assertions are available in the doov-assertions
jar. It depends on AssertJ, so you can use the assertThat
syntax (see wiki section Testing Rules).
ValidationRule rule = DOOV.when(userFirstName.isNotNull().or(userLastName.isNull())).validate();
assertThat(rule).validates(model).hasFailedNodeEmpty();
Build
To build core, assertions, generator core, maven generator plugin and gradle generator plugin modules:
# Core
./gradlew build
# Sample modules with examples
./gradlew -p sample build
To deploy you need to configure the command line options for your repository:
./gradlew \
-Psigning.secretKeyRingFile=secret-file.gpg \
-Psigning.keyId=key-id \
-Psigning.password=password \
-PsnapshotRepository=http://www.acme.com/repository/snapshots \
-Prepository=http://www.acme.com/repository/releases \
-PossrhUsername=userName \
-PossrhPassword=password \
deploy
You can either specify snapshotRepository
or repository
depending on the version type.
To generate documentation with gradle:
# Generate documentation in docs/site/apidocs/subproject
./gradlew javadoc
Release
To release the code, it will create 2 commits with proper tags and versions and push them:
./gradlew \
-Psigning.secretKeyRingFile=secret-file.gpg \
-Psigning.keyId=key-id \
-Psigning.password=password \
-PsnapshotRepository=http://www.acme.com/repository/snapshots \
-Prepository=http://www.acme.com/repository/releases \
-PossrhUsername=userName \
-PossrhPassword=password \
-Pversions.newVersion=RELEASE_VERSION \
release
Licence
[Apache-2.0](LICENSE)
*Note that all licence references and agreements mentioned in the dOOv README section above
are relevant to that project's source code only.