What is the primary interface for handling HTTP requests in Java servlets?
- HttpResponse
- HttpServlet
- ServletInterface
- ServletRequest
The primary interface for handling HTTP requests in Java servlets is ServletRequest.
To listen for events related to a specific attribute in a session, implement the interface ___________.
- HttpSessionActivationListener
- HttpSessionAttributeListener
- HttpSessionBindingListener
- HttpSessionListener
To listen for events related to a specific attribute in a session, implement the HttpSessionAttributeListener interface. This allows tracking changes to attributes within the session.
When a servlet context is initialized or destroyed, the ___________ interface is used.
- ServletContextAttributeEvent
- ServletContextAttributeListener
- ServletContextEvent
- ServletContextListener
The ServletContextListener interface is used when a servlet context is initialized or destroyed, providing methods for handling these lifecycle events.
When a new attribute is added to the session, which listener interfaces are invoked?
- HttpSessionActivationListener
- HttpSessionAttributeListener
- HttpSessionBindingListener
- HttpSessionEvent
The HttpSessionAttributeListener interface is invoked when a new attribute is added to the session. This allows you to perform actions when attributes are added, removed, or replaced in a session.
Identify the listener interface that would be used to log session creation and destruction.
- HttpSessionActivationListener
- HttpSessionBindingListener
- HttpSessionEvent
- HttpSessionListener
The HttpSessionListener interface is used to log session creation and destruction events. This allows you to perform actions when sessions are created or destroyed in a web application.
In a web application, you need to audit changes to session attributes. Which listener would you implement?
- HttpSessionAttributeListener
- HttpSessionBindingListener
- HttpSessionEvent
- HttpSessionListener
The HttpSessionAttributeListener interface is used to audit changes to session attributes. This allows you to perform actions when attributes are added, removed, or replaced in a session.
What is the purpose of the FilterConfig object in Servlet filters?
- To define filter order.
- To hold configuration parameters for a filter.
- To process HTTP requests.
- To store filter mappings.
The FilterConfig object is used to hold configuration parameters for a filter, allowing the filter to be customized without modifying the filter code itself.
How do you specify the URL patterns to which a filter should apply?
- By modifying the servlet code.
- In the filter's constructor.
- In the web server settings.
- Using the
URL patterns to which a filter should apply are specified using the element inside the element in the web.xml file. This defines the URLs that the filter will intercept.
How can a filter access initialization parameters set in the web.xml file?
- By using the FilterConfig object
- By using the HttpResponse object
- By using the HttpServletRequest object
- By using the ServletContext object
A filter can access initialization parameters set in the web.xml file by using the FilterConfig object. This object provides methods to retrieve initialization parameters.
What is the function of FilterMapping in a web application?
- To define the order of filter execution
- To map URL patterns to filter classes
- To map filter classes to servlets
- To specify filter initialization parameters
The function of FilterMapping is to map URL patterns to filter classes. This mapping determines which requests should be intercepted and processed by the associated filter.