architecture Online Quiz - 18

When a JSP is requested, the web container translates it into a servlet class and compiles it. The servlet is then instantiated, creating a servlet instance (object). This instance is initialized and then used to service requests. The servlet instance exists in memory to handle requests to that JSP.

The web.xml file is the standard deployment descriptor for Java web applications. It contains configuration information such as servlet mappings, filter definitions, welcome file lists, context parameters, security constraints, and other application settings. The web container reads web.xml during application deployment to configure the application.

Servlets are designed to handle multiple concurrent requests efficiently. The servlet container typically maintains a single servlet instance per servlet and creates a separate thread for each request. This allows the same servlet instance to service multiple requests simultaneously. Developers must ensure thread-safe code when handling shared resources.

ServletContext provides servlets with access to configuration parameters, server information, and resources shared across the application. It serves as the interface between servlets and their runtime environment, enabling communication with the web container.

The getWriter() method belongs to HttpServletResponse interface and returns a PrintWriter object for sending character-based response data. HttpServletRequest is for incoming request data, while HttpSession manages user session state.

Servlets have three core life-cycle methods: init() for initialization, service() for request processing, and destroy() for cleanup. All are invoked by the container at different stages of the servlet's existence.

Each web application has exactly one ServletContext object shared by all servlets within that application. It provides application-wide scope for attributes and initialization parameters, unlike ServletConfig which is per-servlet.

getParameter() retrieves request parameters sent from the client (form data, query string). getAttribute() retrieves attributes previously set within request scope by the application. getInitParameter() is for servlet configuration parameters.

Servlet containers typically use a thread pool where each request is handled by a separate thread. This makes servlets inherently multi-threaded, requiring careful attention to thread safety when handling shared resources.

The getServletConfig() method returns the ServletConfig object passed to the init() method. This object provides access to servlet-specific initialization parameters. getServletInfo() returns servlet information, and getInitParameters() is not a standard method.

JSP and Servlets are server-side Java technologies that run on the web server and generate dynamic content. HTML is purely client-side markup, and JavaScript (in this traditional context) is primarily a client-side scripting language.

JSP stands for Java Server Pages, a server-side technology that enables the creation of dynamic web content with Java code embedded in HTML templates. It simplifies the development of web applications with a presentation-focused approach.

Modern servlet containers automatically recognize and compile JSP files without requiring explicit configuration in web.xml. JSP files can be placed in the application and accessed directly by their URL, making web.xml configuration unnecessary.

JSP requires a servlet container with JSP support - Apache Tomcat and BEA WebLogic are such servers. JSP Engine is the component within these servers that processes JSP pages. Servlets themselves are not a runtime environment but rather Java classes.

A JSP scriptlet is used to insert Java code into a JSP page and is enclosed within <% and %> delimiters. Other options like <@jsp code %> or <%jsp code %> are syntactically invalid, and <jsp:scriptlet> is the XML equivalent but not styled as shown in the distractors.

JSP comments are server-side comments that use the syntax <%-- comment --%>. These comments are completely removed from the generated output and never sent to the client. HTML comments are client-side and remain in the response. Java-style comments <% // %> or <% /* */ %> are scriptlet code, not JSP comments.

JAR (Java Archive) files contain Java libraries and classes. WAR (Web Application Archive) files are specifically designed for web applications and contain web components like servlets, JSPs, HTML, etc. EAR (Enterprise Archive) files are for J2EE enterprise applications deployed to application servers. Both JAR and WAR files can be deployed in appropriate web servers or servlet containers, making option C correct.

HttpServletRequest.getParameter() retrieves request parameters (form data, query string parameters) from the client. HttpServletResponse does not have a getParameter() method as parameters are only in requests. There is no setParameter() method in HttpServletRequest - parameters are read-only once set. HttpServletResponse.getAttribute() doesn't exist - attributes are on requests, not responses.

Session attributes are stored in the HttpSession object and are accessible to any servlet within the same ServletContext (web application). The ServletContext defines the scope of a web application, so servlets sharing the same context can access session attributes created by any other servlet in that context. This is a fundamental feature of session management for maintaining state across multiple servlet interactions.