All Classes and Interfaces
Class
Description
General application calls.
Commonly used functionality for NIEM supported tools.
Configuration settings for database searches.
General utility functions for the application.
Exception handler for a bad request.
Superclass for a CMF object.
A parent class for all kinds of entities used to represent the structure of a
NIEM model.
Abstract class that provides basic database operations for data model items.
Adds reusable methods for entities that belong to a model: Version, Namespace, Property, etc.
Adds reusable methods for entities that belong to a namespace:
Property, Type, Facet, etc.
Adds reusable methods for entities that belong to a steward: Model, Version, Namespace, etc.
Adds reusable methods for entities that belong to a version: Namespace, Property, etc.
CMF-related utility functions.
A parent class for Property and Type.
Repository interface for finding and managing components in the database.
Operations for managing a component.
Application configuration settings.
Standard supported media types for application responses (JSON, XML).
ISO 3166 Alpha 3 country codes and names.
CSV-related utility functions.
Customized exception handler for database key violations.
Adds JSON as an accepted media type to support cases where the client requests a different
format (like text/csv) and an exception is thrown in JSON.
Custom exception handler for entity not found exceptions.
Custom exception handler for entity not unique exceptions.
A constraint on a datatype, such as an enumeration or a pattern.
Kinds of facet categories, such as enumeration, pattern, and length.
REST controller for facet information.
Repository interface for finding and managing facets in the database.
Operations supporting facets.
Custom exception handler for missing required fields.
File-related utilities to support the application.
Builds a database index for Hibernate searches on an application event.
JSON-related utility functions.
REST controller for migrations.
Migrate a CMF model from one version to any subsequent version.
A reference or message data model.
A kind of model, such as reference, message, or other.
A kind of message objective, such as implementation, example, or test.
REST controller for models.
Repository interface for finding and managing models in the database.
Operations supporting a model.
A collection of properties and types managed by an authoritative source.
Kinds of namespaces, such as core, domain, code, adapter, and extension.
Kinds of schema generation options, representing schemas that have to be
built, schemas that are to be included as static files, and schemas that
do not have to be included at all (e.g., the schema for XML Schema).
Kinds of NDR targets, such as REF and EXT.
REST controller for namespaces.
Repository interface for finding and managing namespaces in the database.
Operations to support namespaces.
Validates XML Schemas against NDR validation rules.
Validates artifacts against NIEM rules.
Exception handler for requests in which no content was found for the given criteria.
A property represents a concept, idea, or thing.
A kind of property indicating whether is is a concrete element, abstract element, or attribute.
REST controller for properties.
Repository interface for finding and managing properties in the database.
Operations supporting properties.
HTTP response-related utility functions.
REST controller for database searches for NIEM and community model content.
Operations to support database searches.
Provides all database services as a convenience.
Gets the user or system interacting with this application for auditing purposes.
A program, group, or other entity responsible for managing NIEM content.
General kinds of stewards, such as Federal, State, Local, Industry, Nonprofit, etc.
REST controller for stewards.
Repository interface for finding and managing stewards in the database.
Operations for managing a steward.
A subproperty is a property that is contained by a type, along with cardinality constraints.
REST controller for subproperties.
Repository interface for finding and managing subproperties in the database.
Operations for subproperties.
Information about a validation test.
Kinds of test severity (error, warning, info).
A test report that consists of a list of tests that may (or may not) have been run.
Supported formats for the validation results file (e.g., json, csv)
An individual test result.
Test result status (error, warning, info, passed, unset).
REST controller for model transformations.
Supported model formats that can be transformed.
Operations to support model transformations.
Supported model transformation output formats.
A type defines a structure - an allowable set of values.
A kind of type, representing CCC types (classes), CSC types (datatype classes)
and simple types (datatypes).
A derivation method for a type, i.e., extension or restriction.
A kind of type pattern with values representing concepts like object, adapter,
association, list, union, etc.
REST controller for types.
Repository interface for finding and managing types in the database.
Operations supporting types.
REST controller for validation.
General operations supporting validation.
Utility functions supporting validation.
A specific version or release of a model.
Kinds of versions, such as major, minor, patch, core supplement, and domain update.
REST controller for versions.
Repository interface for finding and managing versions in the database.
Operations supporting versions.
Custom error handler to catch and log SAX exceptions.
A node to capture the name and style (category) of a node in an XML document.
Maps XML element names to line numbers.
Validate XML files against XML schemas.
XML validation-related utility functions.
Maps XML Schema components (elements, attributes, complex types, and simple types)
to line numbers.
Zipfile-related utility functions.