• Web sites typically use Apache, but Web applications use proprietary Web server applications.
• Web applications provide a mechanism to allow the user to invoke programs running on the Web server
• Sites with over 100 pages are called "Web applications."
• There is no difference. The terms are synonymous.
• Input/Output
• Send/Reply
• Forward/Retrieve
• Request/Response
• GET and POST, the doGet and doPost methods
• SEND and RECEIVE, the service and init methods
• GET and POST, the service and init methods
• REQUEST and RESPONSE, the getRequest and setResponse methods
• /webapps/ROOT/WEB-INF/classes/package
• /webappsIname-of-application/classes/package
• /classes/ROOT/WEB-INF/pacicage
• It does not matter in which directory it is deployed.
• The action attribute must specify the relative URL to the target servlet; the method attribute must specify GET or POST.
• The action attribute must specify the relative URL to the target servlet; the name attribute must provide a unique name for the form.
• The name attribute must provide a unique name for the form, the method attribute must specify the relative URL to the target servlet.
• The action attribute must specify GET or POST, and the method attribute must specify the relative URL to the target servlet.
• NAME, WIDTH, and VALUE
• id, value, and type
• NAME, TYPE, and VALUE
• ACTION, METHOD, and VALUE
• Name-value pairs are sent in the header of the request after the URL.
• Name-value pairs are sent in the body of the request.
• In Hidden fields.
• The complete HTML form, along with the user's responses, is sent after the URL.
• A Servlet object
• A ServletRequest object
• An HttpServletRequest object
• An HttpSession object
• By using the getParameter method on the servlet
• By using the getAttribute method of the HttpSession object
• By using the getinitParameter method on the servlet
• By using the getParameter method of the HttpServletRequest object
• The init, service, and destroy methods
• The do Get and do Post methods
• The doGet, doPost, and doDeiete methods
• The start, init, and paint methods
• The do Get or doPost methods
• The init method
• The service method
• None
• When you need to start a servlet
• When you want to initialize the state of that servlet with initialization parameters
• You should always override the servlet's init method
• You should never override the servlets init method
• The ServletContext object.
• The WebApplication object.
• The ApplicationContext object.
• There is no such object.
• Through the deployment descriptor.
• With the getWebApp method.
• It is always accessible because it is passed to the servlet in the doGet or doPost methods.
• With the getServletContext method.
• A PHP page.
• Java servlet code.
• -An HTML page.
• It does not get translated in the Web container. It is returned to the client and translated by the browser.
• It is compiled into a class file that is stored in the Web container.
• The translated code is sent to the browser.
• It is compiled into a class file that is sent to the browser.
• It is compiled as an applet and then delivered to the client to run in its browser.
• Call the getRequest method of the JSP page.
• Use the getservietconfig method of the JSP page, then call the getRequest method of
• the ServletConfig object.
• There is never a good reason to access the request object from a JSP page.
• None. It is an implicitly defined variable.
• The Web container creates a pool of them at startup time.
• By a slow-roasting process that enhances the flavor and darkens the color
• With the jsp:useBean standard action
• By calling the j spGetBean method
• The context directive.
• The page directive.
• The defineAii directive.
• None. All such properties should be defined in the deployment descriptor.
• With the j sp: forward standard action
• With the j sp: request standard action
• By calling the getRequest method from within a scriptlet tag
• With the j sp: newPage standard action
• JSP pages also serve as the controller in Model 2 architecture.
• Data Access Objects.
• Servlets.
• The HttpServletRequest object.
• JSP pages.
• Data Access Objects.
• Servlets.
• The HttpServletRequest object.
• JSP pages.
• Data Access Objects.
• Servlets.
• The HttpServletRequest object.
• In Model 2 architecture, JSP pages should not be accessing domain objects.
• With the j sp: getBean standard action.
• By mapping the JSP pages to the domain objects with the data-mapping tag in the deployment descriptor.
• With the jsp: useBean standard action.
• Remote method invocation
• Concurrency
• Load-balancing
• Transparent fail-over
• Back end integration
• Dynamic redevelopment
• Clean shutdown
• Logging
Wait!
Here's an interesting quiz for you.