Java Web Programming: Servlets, MVC, and Struts

In the do-while loop, j decrements each iteration. When i increments to 5 (via ++i in the while condition check), ++i < 5 becomes 5 < 5 (false), terminating the loop. At this point, j has decremented four times from 10 to 6, yielding i = 5 and j = 6.

Default (package-private) access is the most restrictive that allows classes in the same package to access members. Public allows access from anywhere, private restricts access to the same class only, and protected allows access to subclasses (even in different packages).

The code in line 13 uses assignment (=) instead of equality comparison (==). In Java, the if condition requires a boolean expression, but x = y results in an integer value, which cannot be converted to boolean. This causes a compilation error.

The compilation fails in Test2 (line 2) because the class extends 'test1.Test1' but this package reference is not imported. To use a class from another package, you need to import it first: 'import test1.Test1;'. Line 2 of Test2 is where Test1 is referenced without an import statement.

First, the loop initialization runs foo('A') (prints A). In the first check, foo('B') (prints B) and i<2 are true; loop body increments i and runs foo('D') (prints D); then update runs foo('C') (prints C). This repeats until the third check where i<2 is false, terminating after printing B.

In ABAP/Reporting, the three main types are: Classical reports (basic list output), Interactive reports (drill-down capability), and List/Grid displays (ALV reports). 'Style report' and 'General Report' are not standard ABAP report classifications.

ActionServlet is the core controller class in Struts Framework - it serves as the front controller that receives all HTTP requests and routes them to appropriate Action classes. ActionServlet is responsible for initializing the framework, populating configuration from struts-config.xml, and managing the request processing lifecycle. Action (Option D) is a class developers extend, not the core controller. Options B and C don't exist in Struts.

The main drawback of Struts 1.x is having only a single controller servlet (ActionServlet), which creates a potential bottleneck since all requests must pass through one point. This can limit scalability and makes it harder to modularize large applications. Options A, B, and D (backword overflow, forward overflow, no forward overflow) are nonsense terms not related to Struts architecture. Struts 2 and later frameworks addressed this by allowing multiple controllers.

A controller in MVC architecture acts as the intermediary between the user (via the view) and the system (model/business logic). It processes user input, coordinates interactions, determines which business logic to execute, and selects the appropriate view for the response. Without a controller, there would be no structured way to handle user requests and map them to system operations.

MVC stands for Model-View-Controller, a design pattern that separates application logic into three interconnected components. The Model handles data and business logic, the View manages the UI presentation, and the Controller processes user input and coordinates Model and View interactions.

MVC1 architecture is tightly coupled because JSP pages handle both presentation (view) and business logic (controller/model). This means changes to business logic require modifying the presentation layer, violating separation of concerns.

The Model component in MVC represents data and business logic. In Java web applications, this is typically implemented using JavaBeans, which encapsulate data and provide methods to access and manipulate it. HTML, servlets, and JSP belong to the View and Controller layers.

The View component in MVC handles presentation and user interface. In Java web applications, JSP (JavaServer Pages) is the standard technology for creating dynamic web content as the view layer. Beans and EJBs belong to Model, Servlets to Controller.

The Controller component in MVC processes user requests and coordinates between Model and View. In Java web applications, Servlets serve as controllers by receiving HTTP requests, processing them, and dispatching to appropriate views (JSP) after updating models (beans).

In MVC2 architecture, a single servlet (often called ActionServlet in Struts) acts as the central controller for all requests. This servlet receives every request, determines which action to invoke, and forwards to appropriate views. This centralized control is a key MVC2 characteristic.

MVC architecture provides reusability (components can be reused across applications), expressiveness (clear separation of concerns), and easier support (changes to one component don't affect others). Option C is incorrect because MVC actually makes applications easier to use and maintain.

Cookies are small pieces of information sent by the web server to the browser, which are then stored and sent back with subsequent requests. They're used for session management, tracking, and remembering user preferences. The server initiates cookie creation.

The doPost() method is used for sending sensitive data because it sends data in the request body (not visible in URL), has no size limit, and is more secure than doGet(). doGet() exposes parameters in the URL, making it unsuitable for sensitive information.

JavaMail API (Java Mail Service) is the standard library for sending email from Java applications, including servlets. It provides classes like Session, Message, and Transport for creating and sending emails through SMTP servers.