Difference between revisions of "Artefact:Model/com/sphenon/basics/exception/ExceptionVerificationFailure"
AndreasLeue (talk | contribs) |
AndreasLeue (talk | contribs) |
||
| Line 27: | Line 27: | ||
cause or location of the error. | cause or location of the error. | ||
'''Caution:''' | |||
Checks throwing these exceptions can typically be disabled for | Checks throwing these exceptions can typically be disabled for | ||
production releases after sufficient testing. In fact, you are | production releases after sufficient testing. In fact, you are | ||
| Line 33: | Line 33: | ||
user input validation or similar purposes. | user input validation or similar purposes. | ||
'''Important:''' | |||
Though it might be tempting to use this class of exceptions | Though it might be tempting to use this class of exceptions | ||
- specifically the subclass [[Artefact:Model/com/sphenon/basics/exception/ExceptionAssertionProvedFalse|ExceptionAssertionProvedFalse]] - | - specifically the subclass [[Artefact:Model/com/sphenon/basics/exception/ExceptionAssertionProvedFalse|ExceptionAssertionProvedFalse]] - | ||
Latest revision as of 13:07, 26 March 2010
| Classification | |
|---|---|
| Type | Type:org/oomodels/WIML/1.0 |
| Domain | Domain:it/test |
| Category | Type:org/oomodels/wiki/Model |
| More | |
| Download Code | |
| Diagram | |
| Namespace (more) | |
| create new pages | |
Code[edit]
| ||||||
| ExceptionVerificationFailure | ||||||
|---|---|---|---|---|---|---|
Description[edit]
A safety check failed. I.e., a check, added for verfication purposes, proved false. Obviously, in normal operation, such errors are not supposed to occur. Therefore the actual reason is unknown, since otherwise it could have been avoided.
The occurence of these failures typically indicate a programming error. The various subclasses provide more information on the presumed cause or location of the error.
Caution: Checks throwing these exceptions can typically be disabled for production releases after sufficient testing. In fact, you are encouraged to do this. Therefore: do not use these exceptions for user input validation or similar purposes.
Important: Though it might be tempting to use this class of exceptions - specifically the subclass ExceptionAssertionProvedFalse - for each and every purpose, to avoid the effort of choosing an appropriate classification, don't take the bait. Firstly, these checks might be disabled, as mentioned, and secondly, software quality depends utterly on useful problem reporting.
