Package multex
MulTEx - the Multi-Tier Exception Handling Framework.
See:
Description
|
Interface Summary |
| MultexException |
Marks an exception as to be handled especially by MsgText.
|
|
Class Summary |
| Assertion |
Tool for checking unexpected programming errors |
| Msg |
Services for reporting messages for exceptions
with parameters (subclasses of Exc)
with cause chain and parameters (subclasses of Failure)
and standard Java exceptions (other subclasses of java.lang.Throwable)
|
| MsgText |
Services for getting the message text for exceptions.
|
|
Exception Summary |
| Assertion.Failure |
Indicates that an assertion failed. |
| Exc |
Problem-related exception with named parameters and internationalizable
message text.
|
| Failure |
Indirectly caused exception with parameters, causal chain and message text.
|
| MethodFailure |
Convenience class, which can be
directly used to be thrown by any failed method. |
Package multex Description
MulTEx - the Multi-Tier Exception Handling Framework.
MulTEx is a simple, but powerful framework for organizing exceptions
and messages is a multi-tier Java software system.
It offers the key features:
- Causal chains as a means to capture low-level error information
- Redundancy-free stack traces in the case of indirectly caused exceptions
- Internationalized message texts and parameters for exceptions
- Services for reporting exceptions onto streams and screens
- A standard way for writing method bodies with regard to exceptions
For introductory information you should first read the technical paper.
This package will still work correctly, if it is renamed,
but you should not put classes of this package into different packages.
Naming conventions
The following naming conventions are used throughout the package multex.
- i_name for in-parameters of methods
- o_name for out-parameters of methods
- io_name for in/out-parameters of methods
- _name for attributes or methods, which should not be used from
outside the class or its subclasses.
Plans
The plans are ordered by priority (most important as No. 1)
- 2000-10-19 MethodFailure should automatically derive the method
and class name from the stack trace.
- 2000-07-31 Introduce a syntax for intentional suppressing of an
exception parameter in a message text pattern. The planned sytax is:
{name-} for suppressing a named parameter.
Version history
- 1.0 of 2000-10-21 Big revolution.
- New convenience class MethodFailure. No longer 0..10
unnamed parameters in Failure-constructor.
- Each exception object has a default message text pattern, which is used,
if there is no corresponding message text found in file MsgText.properties or one of its
localized variants.
- New classes Assertion and Assertion.Failure
- Requires only JDK 1.1, no longer 1.2
- 0.2 of 2000-10-08 Failure extends java.lang.RuntimeException by default.
- 0.1 of 2000-09-29 Failure extends java.lang.Exception instead of
multex.Exc. Thus it is easily switchable to extends java.lang.RuntimeException.
Named parameters are the only parameters, that can be inserted into a
message text. Nevertheless for easiest providing of diagnostic information
in a Failure exception, the constructor of Failure accepts 0..10 unnamed
parameters of type Object.
- 0.0 of 1999..2000 Evolution of this framework