Head First Servlets and JSP, 2nd Edition

SkipPageException stops only the page that directly invoked the tag

If the page that invokes the tag was included from some other page, only the page that invokes the tag stops processing! The original page that did the include keeps going after the SkipPageException.

PageB (the included file) JSP that invokes the bad tag

The tag handler doTag() method

public void doTag() throws JspException, IOException {
   getJspContext().getOut().print("Message from within doTag().<br>");
   getJspContext().getOut().print("About to throw a SkipPageException");
   throw new SkipPageException();
}

Note

This stops page B, but page A keeps going.

There are no Dumb Questions

Q:	Q: What happens to a SimpleTag handler after it completes doTag()? Does the Container keep it around and reuse it?
A:	A: No. SimpleTag handlers are never reused! Each tag handler instance takes care of a single invocation. So you never have to worry, for example, that instance variables in a SimpleTag handler won’t have the correct initial values. A SimpleTag handler object will always be initialized before any of its methods are called.
Q:	Q: Do the attribute methods in a SimpleTag handler have to be of a type that can be automatically converted to and from a String? In other words, are you stuck with just primitives and String values?
A:	A: Weren’t ...