Implementation of PRePServlet
| |
First of all the init() method of the PRePServlet will be called from the servletrunner. There a new PRePHandler (providePRePHandler()) will be created as well as the ConnectionPool initialised (default values). You may specify (if you create a subclass) how many connections you will need for your servlet. The default size is 5. As soon as a request from the servletrunner arrives, the handle() method of the PRePServlet is called. This method handles the request and does everything from setting the PrintWriter to the login and finally output of the PRePFile. It is build out of different methods which all work over the PRePHandler. The PRePHandler is unique - unlike the PRePMain which is given to the PRePServlet at the beginning. It will be deleted after the handle() method finished. If the servletrunner closes, it calls the destroy() method of the PRePServlet class which itself calls the destroy() method of the PRePHandler class. The ConnectionPool will be destroyed and its connection closed one for one. Constructor:
Methods:
init(ServletConfig servletConfig)
![]()
handle(HttpServletRequest req, HttpServletResponse res)
![]()
getPRePMain()
setPrintWriter(Instance instance)
putPRePTags(Instance instance)
setParams(Instance instance)
setCookies(Instance instance)
setContext(Instance instance)
getNewCookies(Instance instance)
loginOk(Instance instance)
loginNotOk(Instance instance)
finishHandle(Instance instance)
destroy()
![]() |
|
|
Other information about PRePServlet |