All Exceptions that can provide additional information about the place where the error happened (template name, column and line number) can implement this interface and the ParseErrorException will then be able to deal with this information.
Application-level exception thrown when macro calls within macro calls exceeds the maximum allowed depth.
Separate exception class to distinguish math problems.
Application-level exception thrown when a reference method is invoked and an exception is thrown.
Application-level exception thrown when a resource of any type has a syntax or other error which prevents it from being parsed.
Application-level exception thrown when a resource of any type isn't found by the Velocity engine.
Exception generated to indicate parse errors caught during directive initialization (e.g.
Base class for Velocity runtime exceptions thrown to the application layer.