Package net.sourceforge.argval

Each class with public methods / constructors, should check it's incoming arguments (the preconditions).

See:
Description

Interface Summary

ArgumentValidation
ConfigurationManager

Package net.sourceforge.argval Description

Each class with public methods / constructors, should check it's incoming arguments (the preconditions). Doing this can be quite cumbersome and many times you're doing the same things over and over again. Keeping the output texts similar and nice formated is already a task on it's own. An other thing which mostly is not done, check all the arguments and their needed conditions, before actually throwing the IllegalArgumentException. If a String value needs to be within a certain collection, an error will be shown contain the possible values if the given value was not within the collection.

Some of the supported argument checks are:

• incoming Object is a not null
• incoming String is a Boolean
• incoming String is a Integer
• incoming String has a minimal length of x
• incoming String has a maximal length of y
• incoming String has a minimal length of x and a maximal length of y
• incoming String has a exact length x
• incoming String is part of a known set
• incoming integer is greater then x
• incoming String matches a date format pattern
• incoming String matches a regular expression

The usage of the Java Argument Validation is described in ArgumentValidation.