What is the initial contact point for handling a web request in a Page-Centric architecture?
-
A JSP page
-
A JavaBean
-
A servlet
-
A session manager
In a page‑centric web architecture the first component that receives the HTTP request is a JSP page, which processes the request directly or includes other resources. Servlets or beans are typically invoked later, making the JSP the initial contact point.
To answer this question, you need to understand the concept of a Page-Centric architecture.
In a Page-Centric architecture, the web request is first handled by a specific page. Each page is responsible for handling a specific request and generating the appropriate response.
Let's go through each option to understand why it is correct or incorrect:
Option A) A JSP page - This option is correct because in a Page-Centric architecture, a JSP (JavaServer Pages) page is often used as the initial contact point for handling a web request. The JSP page contains a mix of HTML and Java code and can be used to generate dynamic content.
Option B) A JavaBean - This option is incorrect. A JavaBean is a reusable software component that follows certain naming conventions. While JavaBeans can be used in a Page-Centric architecture, they are not the initial contact point for handling a web request.
Option C) A servlet - This option is incorrect. A servlet is a Java program that runs on a web server and handles client requests. While servlets can be used in a Page-Centric architecture to handle web requests, they are not the initial contact point.
Option D) A session manager - This option is incorrect. A session manager is responsible for managing user sessions in a web application. While a session manager is an important component of a web application, it is not the initial contact point for handling a web request in a Page-Centric architecture.
The correct answer is A) A JSP page. This option is correct because in a Page-Centric architecture, a JSP page is often used as the initial contact point for handling a web request.