Package bsh

Class TargetError

All Implemented Interfaces:
Serializable

public final class TargetError extends EvalError
TargetError is an EvalError that wraps an exception thrown by the script (or by code called from the script). TargetErrors indicate exceptions which can be caught within the script itself, whereas a general EvalError indicates that the script cannot be evaluated further for some reason. If the exception is caught within the script it is automatically unwrapped, so the code looks like normal Java code. If the TargetError is thrown from the eval() or interpreter.eval() method it may be caught and unwrapped to determine what exception was thrown.
See Also:
  • Constructor Details

    • TargetError

      public TargetError(String msg, Throwable t, bsh.SimpleNode node, CallStack callstack, boolean inNativeCode)
    • TargetError

      public TargetError(Throwable t, bsh.SimpleNode node, CallStack callstack)
  • Method Details

    • getTarget

      public Throwable getTarget()
    • toString

      public String toString()
      Overrides:
      toString in class Throwable
    • getMessage

      public String getMessage()
      Description copied from class: EvalError
      Print the error with line number and stack trace.
      Overrides:
      getMessage in class EvalError
    • printStackTrace

      public void printStackTrace()
      Overrides:
      printStackTrace in class Throwable
    • printStackTrace

      public void printStackTrace(PrintStream out)
      Overrides:
      printStackTrace in class Throwable
    • printStackTrace

      public void printStackTrace(boolean debug, PrintStream out)
    • inNativeCode

      public boolean inNativeCode()
      Return true if the TargetError was generated from native code. e.g. if the script called into a compiled java class which threw the excpetion. We distinguish so that we can print the stack trace for the native code case... the stack trace would not be useful if the exception was generated by the script. e.g. if the script explicitly threw an exception... (the stack trace would simply point to the bsh internals which generated the exception).