Java Enterprise and Web Technologies

getSession() (no-arg) and getSession(true) both create a new session if one doesn't exist. getSession(false) returns null if no session exists, without creating one. The createSession() methods do not exist in the HTTPServletRequest API.

sendRedirect(String url) is the correct method on HttpServletResponse to redirect the client to a different URL. This sends a temporary redirect (HTTP 302) to the browser. getRequestDispatcher() is for server-side forwards, not redirects.

In JSP, 'application' is a valid implicit variable representing the ServletContext. Other implicit objects include request, response, session, out, pageContext, config, and page. 'stream', 'context', and 'listener' are not standard JSP implicit variables.

JSP lifecycle includes jspInit() for initialization and jspDestroy() for cleanup, both of which can be overridden by developers. The _jspService() method is generated by the container and cannot be overridden - it's where your JSP code ultimately executes.

Valid JSP directives are page, taglib, and include. 'import' is not a directive itself - it's an attribute of the page directive used for importing Java classes. Directives always start with <%@ and end with %>.

The jsp:forward standard action uses the 'page' attribute to specify the target resource, not 'file'. The correct syntax is . There is no 'dispatch' standard action in JSP.

A tag is considered empty only if it has no body content. Option D contains a scriptlet (<%=...%>) which produces output, giving it body content. Options A, B, and C are truly empty - A uses self-closing syntax, B has no content between tags, and C uses jsp:attribute for setting attributes.

The Siebel Web Engine's core function is receiving a URL request, gathering the appropriate templates and data from the database, and constructing an HTML page to return. It doesn't display the page (browser does), distribute load (that's the SWSE), or verify browsers (client-side check).

In page flow frameworks, the getPageFlowController() method can indeed be overridden to specify or customize the page flow controller for a particular page or scenario. This is standard practice for customizing navigation flow behavior. The correct answer is True.

PsPageData is the object that provides page authors with consistent, standardized access to application data. PsPageMetaData contains metadata information, PsPageFlowController handles navigation logic, and PsPageMetaDataReader is for reading metadata - none of these provide the data access mechanism.

A JSP tag library consists of three key components: the Tag Library Descriptor (TLD) file that defines the tags (C), the actual implementation code for each tag (D), and the JSP code that uses the tags (E). Bean name (A) is not a component of the tag library itself - it's data managed by the bean. Servlet code (B) is not directly part of tag library structure. Options C, D, and E are correct.

To build a composite JSP page dynamically at runtime, the standard action tag `` is used to merge the content of another resource into the current page.

The HttpServlet class in Java Servlets provides lifecycle methods corresponding to HTTP methods, including doGet(), doTrace(), and doOptions(). Therefore, all of the listed options are valid methods.

ServletConfig is one per servlet, not per web application. Each servlet gets its own ServletConfig object during initialization containing its specific initialization parameters. For web application-wide configuration, you use ServletContext, which is shared across all servlets in the application.

The Hibernate configuration XML uses as its root element. This element contains which in turn contains property definitions and mapping resources. Alternative names like or are not valid Hibernate configuration elements.