Parentpacke: Consultingwerk.OERA
Consultingwerk.OERA.ValidationMessages

The Consultingwerk.OERA.ValidationMessages package contains core classes that allow the serialization of validation messages in a CCSBE compatible format.

See Section 2.5 Component Error Handling of the CCSBE spec:

In any situation where a Business Entity method is not able to perform it's task it is expected to throw errors to its caller. The error message MUST state clearly the nature of the error preventing the Business Entity to perform the task and the error is expected to provide useful additional properties for analysis and logging. It is strongly advised to throw error objects with error messages and not with the legacy ReturnValue (e.g. using the AppError constructor with a CHARACTER and an INTEGER parameter instead of just a single CHARACTER parameter).

In the current revision the CCSBE specification will not enforce different error classes or interfaces to be used for different error scenarios.

Data Validation during update operations is considered an application function and a key behaviour of the (Updatable) Business Entity. As such validation errors (the consumer passes data for update to the Business Entity that does not match the requirements of the Business Logic such as empty fields, data values out of range, foreign key violations etc.) are not expected to be thrown to the caller. Validation error are not runtime errors; they are part of the business logic functionality of a Business Entity. These validation errors are returned to the caller using the mechanisms of ProDataset member records (the ERROR and ERROR-STRING attribute of the member record as well as the ERROR attribute of the ProDataset itself).

Validation messages returned through the ERROR-STRING attribute of the temp-table records are recommended to be encoded in such a way that the Message Manager (defined by CCS later) is able to return a localized error message to the consumer.

Business Entity implementation that should remain usable outside of a full blown CCS implementation SHOULD be prepared to return validation messages directly in a human understandable form as the Message Manager of the CCS may not be available.

As multiple separate validation messages (for different fields) MAY need to be returned those messages are expected to be returned as a JSON array. Each object in the JSON array MUST provide the following properties if applicable:

Property Description
FieldName The name of the field that caused this error. Leave blank if the error is caused by the whole record
MessageStrings The JSON string array of full unencoded error messages, one string per line.
MessageId The numeric identifier of an error message.
MessageGroup The error message group
SubstitutionValues The JSON string array of values to substitute placeholder (&1, &2, &3, ...) in the message template identified by MessageId and MessageGroup
Severity A string with is either "Info", "Warning" or "Error"

The Business Entity SHOULD either set the MessageId and MessageGroup or the MessageStrings property in the message structure. MessageId and MessageGroup are typically passed on the client or the service interface to a Message Manager component for retrieving a localized message.

If one or more JSON Array elements for MessageStrings is provided the MessageId, MessageGroup and SubstitutionValues MAY be left empty.

The MessageId (message number) and MessageGroup are used to retrieve a message template string from a Message Manager.

Empty JSON properties are not supposed to be contained in the ERROR-STRING property of the ProDataset member record.

Classes
ListValidationMessage List of ValidationMessage instances
ValidationMessage Describes a validation message

Enums
ValidationMessageSeverity Enum of values for the Severity property of the ValidationMessage class

©2006-2019 Consultingwerk Ltd.         info@consultingwerk.de         http://www.consultingwerk.de       09.08.2019 00:10:08