Java Enterprise and Web Technologies

Java web server Tomcat is a servlet container that implements servlets. Apache web server is a pure HTTP server (not a servlet container), and HttpURLConnection is a client-side class for making HTTP requests.

JSP provides implicit objects like out, request, response, session, and page that can be used directly in expressions. 'httpsession' is not a valid JSP implicit variable - the session object itself is an HttpSession, not a variable called 'httpsession'. Options A, B, C, D, and F are all standard implicit objects available in JSP expressions.

Option A correctly states that ServletContext.getRequestDispatcher uses full paths (starting with '/'), while HttpServletRequest.getRequestDispatcher uses paths relative to the current context. Option C is also correct - both interfaces define getRequestDispatcher with different path resolution rules. Option B is incorrect because include can be invoked after output. Option D is wrong because getNamedDispatcher is in ServletContext, not HttpServletRequest.

Router, Notify, and Utility shapes in Pega flows are all based on the Rule-Obj-Activity rule type. These are technically specialized flow shapes that internally invoke activities. In the Security tab of an Activity rule, you can see that Router, Notify, and Utility are all listed as activity-based rule types. They are not separate rule types from Rule-Obj-Activity - they are specialized implementations that use activities as their foundation.

In JSF, the full expression #{facesContext.externalContext.requestContextPath} accesses the external context to retrieve the request’s context path, which is the correct way to reference the application’s base URL. The other shorter forms either reference non‑existent properties or use the wrong EL syntax, making them incorrect.

HttpServlet class provides doGet(), doTrace(), doOptions(), doPost(), doPut(), doDelete(), and other methods corresponding to HTTP protocol verbs. Since doGet, doTrace, and doOptions are all valid HttpServlet methods, 'All the Above' is the correct answer.

JSP (JavaServer Pages) is built on servlet technology. During deployment, JSP pages are compiled into servlets by the container. Servlets are the underlying technology, not the other way around. JSP provides a template-based approach for generating dynamic content, but ultimately executes as servlets.

In Java Servlet API, both GenericServlet (a protocol-independent servlet) and HttpServlet (a servlet specifically tailored for HTTP requests) are types of servlets. Therefore, both are valid servlet implementations, making the option "Both (A) and (B)" correct.

In Page-Centric architecture, the JSP page itself is the initial contact point for handling web requests. Unlike servlet-centric architectures where a servlet receives and processes requests first, page-centric designs route requests directly to JSP pages which may then delegate to beans or other components as needed.

To process form submissions in a servlet, you subclass HttpServlet and override the doGet() or doPost() methods, depending on the HTTP request method used. The service() method automatically dispatches requests to these methods, so developers rarely need to override service() directly.

WCF's webHttpBinding is specifically designed for RESTful services, enabling communication with XML or JSON payloads, which makes it ideal for ASP.NET AJAX clients. The basicHttpBinding and wsHttpBinding are built for SOAP-based web services, which are less suitable for standard Ajax clients.

The init() method is the designated place for servlet initialization code in the Servlet API lifecycle. It's called once when the servlet is first loaded. The service() method handles each request. The constructor is not the standard initialization point for servlets - init() guarantees the ServletConfig is available.

Servlet mapping is the association between a URL pattern and a servlet, defined in web.xml (or annotations). It tells the container which servlet should handle requests matching specific URL patterns. ServletContext is shared data across servlets. Lifecycle refers to servlet initialization/destruction. The mapping mechanism is essential for routing requests to correct servlets.

All Servlets must implement the javax.servlet.Servlet interface, which defines the lifecycle methods (init, service, destroy) that the servlet container calls. Servlet mapping is a configuration concept, and Servlet Container is the runtime environment, not an interface to implement.

Apache Tomcat is a widely used web server and servlet container that implements the Java Servlet specification. Apache HTTP Server is a general web server without servlet support, and HttpURLConnection is a client-side API class, not a servlet implementation.