java.lang.Object
java.lang.Throwable
java.lang.Exception
com.presumo.jms.selector.SelectorFalseException
- All Implemented Interfaces:
- java.io.Serializable
- public final class SelectorFalseException
- extends java.lang.Exception
JMS defines some conditions that will always render a selector
false. One example is trying to add two strings. While the
parser can detect errors in literals at parse time, it can not
tell what type an identifier is until evaluation time. If an
identifier type is incorrectly used JMS says that the selector
is invalid. Another example would be referencing an object
property from anywhere in the sql expression.
The evaluate methods will throw this exception if they encounter
a situation like the ones above. This will effectively short-circuit
the evaluation. If you call evaluate on the node in the expression
tree you must catch this exception. If it occurs you can assume
the selector is false. If the selector does not throw an
exception you still have to check the return type to see if
the evaluation was true or false or unknown. (unknown == false).
| Nested classes inherited from class java.lang.Throwable |
|
| Fields inherited from class java.lang.Exception |
|
| Fields inherited from class java.lang.Throwable |
|
| Methods inherited from class java.lang.Throwable |
fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString |
onlyInstance
private static SelectorFalseException onlyInstance
SelectorFalseException
private SelectorFalseException()
getInstance
static SelectorFalseException getInstance()