/* * The Apache Software License, Version 1.1 * * Copyright (c) 1999 The Apache Software Foundation. All rights * reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in * the documentation and/or other materials provided with the * distribution. * * 3. The end-user documentation included with the redistribution, if * any, must include the following acknowlegement: * "This product includes software developed by the * Apache Software Foundation (http://www.apache.org/)." * Alternately, this acknowlegement may appear in the software itself, * if and wherever such third-party acknowlegements normally appear. * * 4. The names "The Jakarta Project", "Tomcat", and "Apache Software * Foundation" must not be used to endorse or promote products derived * from this software without prior written permission. For written * permission, please contact apache@apache.org. * * 5. Products derived from this software may not be called "Apache" * nor may "Apache" appear in their names without prior written * permission of the Apache Group. * * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * ==================================================================== * * This software consists of voluntary contributions made by many * individuals on behalf of the Apache Software Foundation. For more * information on the Apache Software Foundation, please see * . * */ package javax.servlet.jsp; import java.io.IOException; import java.util.Enumeration; import javax.servlet.Servlet; import javax.servlet.ServletConfig; import javax.servlet.ServletContext; import javax.servlet.ServletException; import javax.servlet.ServletRequest; import javax.servlet.ServletResponse; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpSession; import javax.servlet.jsp.tagext.BodyContent; /** *

* A PageContext instance provides access to all the namespaces associated * with a JSP page, provides access to several page attributes, as well as * a layer above the implementation details. Implicit objects are added * the pageContext automatically. * *

The PageContext class is an abstract class, designed to be * extended to provide implementation dependent implementations thereof, by * conformant JSP engine runtime environments. A PageContext instance is * obtained by a JSP implementation class by calling the * JspFactory.getPageContext() method, and is released by calling * JspFactory.releasePageContext(). * *

An example of how PageContext, JspFactory, and other classes can be * used within a JSP Page Implementation object is given elsewhere. * *

* The PageContext provides a number of facilities to the page/component author and * page implementor, including: *

* *

Methods Intended for Container Generated Code *

Some methods are intended to be used by the code generated by the * container, not by code written by JSP page authors, or JSP tag library authors. *

The methods supporting lifecycle are initialize() * and release() * *

* The following methods enable the management of nested JspWriter streams to * implement Tag Extensions: pushBody() and popBody() * *

Methods Intended for JSP authors *

* Some methods provide uniform access to the diverse objects * representing scopes. * The implementation must use the underlying Servlet machinery * corresponding to that scope, so information can be passed back and * forth between Servlets and JSP pages. The methods are: * setAttribute(), getAttribute(), * findAttribute(), removeAttribute(), * getAttributesScope() and getAttributeNamesInScope() . * *

* The following methods provide convenient access to implicit objects: *