Class PageServlet
- All Implemented Interfaces:
jakarta.servlet.Servlet, jakarta.servlet.ServletConfig, Serializable
*.mp extension).
All uncaught exceptions in the rendered page are wrapped in a ServletException and thrown up to the servlet container. These are typically handled by the container by either showing the full stack trace to the user or using a error page configured in the containers web.xml file. This latter approach is recommended for production use. An example is shown below.
invalid input: '<'error-page> invalid input: '<'exception-type>java.lang.Exceptioninvalid input: '<'/exception-type> /errors/error.mp invalid input: '<'/error-page>
However, if some partial response has already been sent to the browser and an exception occurs (later in java code on that same page), then the error page (if configured in web.xml) cannot typically be displayed.
For that scenario, this servlet accepts an optional error_page initialization parameter. This parameter, if present, should contain a webapp-relative path to an error page that will be included in the rendered page if there is an exception after the response has been committed. This error page is then included in the response sent to the browser.
The following attributes are available in the error page
jakarta.servlet.error.status_code jakarta.servlet.error.exception jakarta.servlet.error.request_uri jakarta.servlet.error.servlet_name
This servlet also accepts an optional 404_page parameter. This parameter, if present, should contain a web document root-relative path to a 404 or not found page. This page is different than the error_page because it signifies a badly typed URL request for a page that does not exist. (for example, http://somehost/badpage.mp). This parameter should be the same as the 404 error code parameter in web.xml. For example:
invalid input: '<'error-page> invalid input: '<'error-code>404invalid input: '<'/error-code> /errors/not_found.html invalid input: '<'/error-page>
- See Also:
-
Field Summary
Fields inherited from class jakarta.servlet.http.HttpServlet
LEGACY_DO_HEAD -
Constructor Summary
Constructors -
Method Summary
Methods inherited from class FCBaseServlet
getLog, statsMethods inherited from class jakarta.servlet.http.HttpServlet
serviceMethods inherited from class jakarta.servlet.GenericServlet
getInitParameter, getInitParameterNames, getServletConfig, getServletContext, getServletInfo, getServletName, init, log, log
-
Constructor Details
-
PageServlet
public PageServlet()
-
-
Method Details
-
init
- Specified by:
initin interfacejakarta.servlet.Servlet- Overrides:
initin classFCBaseServlet- Throws:
jakarta.servlet.ServletException
-
toString
- Overrides:
toStringin classFCBaseServlet
-
destroy
- Specified by:
destroyin interfacejakarta.servlet.Servlet- Overrides:
destroyin classFCBaseServlet
-