Package org.media.mn8.event

MN8 Event Classes.

See:
          Description

Class Summary
ElementAccessEvent  
 

Exception Summary
AttributeNotFoundException  
ConceptNotFoundException  
ElementNotFoundException  
FieldNotFoundException  
ForcedInstance  
FTPOperationFailure  
MethodNotFoundException  
mn8ConceptInstantiationException  
mn8Error  
mn8Exception The basic mn8 exception class.
mn8ExitEvent Exception thrown for general system related errors or warnings.
mn8IndexOutOfBoundsException  
mn8NotImplementedException  
mn8NoURIHandler  
mn8OperationNotSupported  
mn8ResourceLoadingException  
mn8SystemException Exception thrown for general system related errors or warnings.
mn8Warning  
NotLogicalExpressionException  
NotStaticAttributeException  
NotStaticElementException  
NotStaticMethodException  
UnexpectedError  
 

Package org.media.mn8.event Description

MN8 Event Classes.

This package contains the mn8 event classes.

The basic vision is that, during the interpretation many events can occur. System errors like some component are unable to get initialized so the mn8 Interpreter is compromised, or some exception occurred during interpretation and the user has to be made aware of it's errors.

Also there might be different needs for the information amount to be presented. Most obviously most non technical users will be confused if we provide unrelevant information for them and most technical users will need more informations in order to know what is happening.

Handling all this different informations amount separately for each case would mean a lot of work, which is very error prone, all of use use to forget things from time to time.

In this idea all the exceptional (not direct information, mn8 related) will be propagated using events. By having different event type, we will be able to differentiate the kind of errors and act based on this. So these event types are only carriers of messages and differentiators. They deliver the information to anyone interested in it, letting it decide what to do with it, and how much to expose from it.

As I said the event classes are only carriers. The information is formatted by the special formatter classes. In the command line interpreter the LogManager is responsible to show the user the message. Also based on the -v (--verbose) or -d (--debug) switches will expose less or more from this information to the user.

As an example, without any kind of switches it will only display the info of the message. With the -v (--verbose) switch will show the info and the event.getMessage() of the generator event. With the -d (--debug) switch will shot also the event.printStackTrace().

Version:
$Revision: 1.2 $ $Date: 2002/10/18 22:02:57 $
Author:
Remus Pereni


"Copyright © 2000-2002 Internet Multicasting Services, media.org & noLimits Technologies. All Rights Reserved."