Uses of Package net.protempore.utils

Overview

Package

Class

Use

Tree

Deprecated

Index

Help

PREV NEXT

FRAMES NO FRAMES

Uses of Package
net.protempore.utils

Packages that use net.protempore.utils
net.protempore.utils

Classes in net.protempore.utils used by net.protempore.utils
BaseRuntimeException A base runtime exception class that provides 2 additional conveniences: 1) it allows a variable number of arguments to be given in addition to the message, which will be interpolated into the message if there is at least 1; 2) there are overloaded constructors allowing for an array of `Throwable` instead of just a single `Throwable`, which is useful when an exception may only be thrown at the end of a method, and multiple underlying exceptions may be the cause of the end exception thrown.
Validator A simple validator intended to be a standalone validation class that takes advantage of JDK5+ features that ease common validation tasks (like error messages with arguments that don't get formatted into the message if the assertion doesn't fail), as well as being more configurable in terms of reacting to failed assertions (at present, we can throw a user-configuration runtime exception and/or log using built-in Java logging).

Classes in net.protempore.utils used by net.protempore.utils

BaseRuntimeException
A base runtime exception class that provides 2 additional conveniences: 1) it allows a variable number of arguments to be given in addition to the message, which will be interpolated into the message if there is at least 1; 2) there are overloaded constructors allowing for an array of Throwable instead of just a single Throwable, which is useful when an exception may only be thrown at the end of a method, and multiple underlying exceptions may be the cause of the end exception thrown.

Validator
A simple validator intended to be a standalone validation class that takes advantage of JDK5+ features that ease common validation tasks (like error messages with arguments that don't get formatted into the message if the assertion doesn't fail), as well as being more configurable in terms of reacting to failed assertions (at present, we can throw a user-configuration runtime exception and/or log using built-in Java logging).