One of the rules for a class which a JSP page will extend states that the JSP
engine should check that for the superclass:

        o       All of the methods in the Servlet interface are declared final

Is that right?

For instance, the tag:

        <%@ page info="Info String" %>

Wouldn't this make the generated class override the getServletInfo() class?  If
the superclass's getServletInfo() method was declared final, this would generate
an error.

Also, what if I had a JSP page superclass which I wanted to extend?  Say I
wanted to initalize more resources in the init() method?  I wouldn't be able to
leverage the code in the original JSP superclass.

I noticed that the jswdk-1.0 didn't enforce this rule.  The 1.1 spec still had
this rule as well.  It seems to me that this rule doesn't really serve much
purpose.

Comments?  Or can somebody explain the logic behind this rule?

Thanks,
Rich

-------------------------
Richard M. Yumul
mailto:[EMAIL PROTECTED]
DTAI Incorporated
http://www.dtai.com
(619)542-1700 � fax:(619)542-8675

===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
 http://java.sun.com/products/jsp/faq.html
 http://www.esperanto.org.nz/jsp/jspfaq.html

Reply via email to