Advanced Java Programming (4351603) - Winter 2024 Solution

Question 1(a) [3 marks]

#

Describe JFC with its usage.

Answer:

JFC (Java Foundation Classes) is a comprehensive GUI framework for building desktop applications in Java.

• Primary Usage: Creating rich desktop applications
• Key Advantage: Platform independence and consistent look

Mnemonic: “JFC = Java’s Fantastic Components”

Question 1(b) [4 marks]

#

Explain Difference between AWT and Swing.

Answer:

• AWT Limitation: Limited components, platform-specific appearance
• Swing Advantage: Rich component set, customizable UI

Mnemonic: “AWT = Always Weighs Too-much, Swing = Simply Works In New Generation”

Question 1(c) [7 marks]

#

List out various Event Listener. Explain anyone.

Answer:

Event Listeners List:

ActionListener Explanation:

• Interface Method: actionPerformed(ActionEvent e)
• Usage: Handles button clicks and menu actions
• Implementation: Anonymous class or lambda expression

button.addActionListener(e -> {
    System.out.println("Button clicked!");
});

Mnemonic: “AMKWFI Listeners = Action Mouse Key Window Focus Item”

Question 1(c OR) [7 marks]

#

List out various Layout Managers. Explain anyone.

Answer:

Layout Managers List:

BorderLayout Explanation:

• Default Layout: For JFrame and JDialog
• Five Regions: North, South, East, West, Center
• Resizing: Center expands, others stay preferred size

graph LR
    A[North] 
    B[West] 
    C[Center] 
    D[East]
    E[South]
    
    A --- B
    A --- C
    A --- D
    B --- C
    C --- D
    B --- E
    C --- E
    D --- E

Mnemonic: “FBGCBG Layouts = Flow Border Grid Card Box GridBag”

Question 2(a) [3 marks]

#

List out and explain steps to connect database.

Answer:

Database Connection Steps:

Mnemonic: “LCD EPR = Load Create Driver, Execute Process Results”

Question 2(b) [4 marks]

#

Explain 3-tier architecture with diagram.

Answer:

3-tier architecture separates application into three logical layers for better maintainability.

graph LR
    A[Presentation Tier<br/>Web Browser/UI] 
    B[Application Tier<br/>Business Logic/Servlets] 
    C[Data Tier<br/>Database Server]
    
    A <--> B
    B <--> C

• Advantage: Better scalability and maintainability
• Example: Web browser → Web server → Database

Mnemonic: “PAD = Presentation Application Data”

Question 2(c) [7 marks]

#

Describe JDBC API with interfaces and classes.

Answer:

JDBC API Components:

JDBC Architecture:

graph LR
    A[Java Application] --> B[JDBC API]
    B --> C[JDBC Driver Manager]
    C --> D[JDBC Driver]
    D --> E[Database]

• Core Interfaces: Connection, Statement, ResultSet, PreparedStatement
• Key Classes: DriverManager for connection management
• Exception Handling: SQLException for database errors

Mnemonic: “CSRP Classes = Connection Statement ResultSet PreparedStatement”

Question 2(a OR) [3 marks]

#

List out advantages and disadvantages of JDBC.

Answer:

JDBC Advantages vs Disadvantages:

• Benefits: Write once, run anywhere with any database
• Drawbacks: Requires manual SQL and connection management

Mnemonic: “PSM vs PCL = Platform Standard Multiple vs Performance Complex Limited”

Question 2(b OR) [4 marks]

#

Explain 2-tier architecture with diagram.

Answer:

2-tier architecture directly connects client to database server.

graph LR
    A[Client Tier<br/>Application/UI] <--> B[Data Tier<br/>Database Server]

• Advantage: Simple architecture, direct communication
• Disadvantage: Limited scalability, tight coupling
• Example: Desktop application connecting directly to database

Mnemonic: “CD = Client Data (direct connection)”

Question 2(c OR) [7 marks]

#

List out JDBC driver types and Explain TYPE-4.

Answer:

JDBC Driver Types:

TYPE-4 Driver Explanation:

• Pure Java: Completely written in Java
• Direct Communication: Directly communicates with database
• Platform Independent: No native libraries required
• Best Performance: Fastest among all types
• Examples: MySQL Connector/J, PostgreSQL JDBC

graph LR
    A[Java Application] --> B[Type-4 JDBC Driver<br/>Pure Java] --> C[Database Server]

Mnemonic: “ONNN Drivers = ODBC Native Network Native-pure”

Question 3(a) [3 marks]

#

Explain Application of servlet.

Answer:

Servlet Applications:

• Primary Use: Server-side Java programs for web applications
• Common Tasks: Request processing, response generation

Mnemonic: “WDSF = Web Database Session File”

Question 3(b) [4 marks]

#

Explain difference between Applet and Servlet.

Answer:

• Applet: Runs in web browser, limited capabilities
• Servlet: Runs on web server, full Java capabilities

Mnemonic: “Client vs Server = Applet vs Servlet”

Question 3(c) [7 marks]

#

Explain life cycle of a servlet in detail.

Answer:

Servlet Life Cycle:

graph LR
    A[Servlet Class Loaded] --> B[init called]
    B --> C[service handles requests]
    C --> C
    C --> D[destroy called]
    D --> E[Servlet Unloaded]

• Thread Safety: Multiple requests handled concurrently
• Single Instance: One servlet instance handles all requests
• Container Managed: Web container manages lifecycle

Mnemonic: “LISD = Load Init Service Destroy”

Question 3(a OR) [3 marks]

#

Explain web.xml file in servlet.

Answer:

web.xml Purpose:

• Location: WEB-INF directory
• Format: XML configuration file

Mnemonic: “DMI = Deployment Mapping Initialization”

Question 3(b OR) [4 marks]

#

List out and Explain feature of servlet.

Answer:

Servlet Features:

• Performance: Better than CGI scripts
• Scalability: Handles multiple requests efficiently

Mnemonic: “PSPPS = Platform Server Protocol Persistent Secure”

Question 3(c OR) [7 marks]

#

Explain session tracking in servlet.

Answer:

Session Tracking Methods:

HttpSession Implementation:

HttpSession session = request.getSession();
session.setAttribute("user", username);
String user = (String) session.getAttribute("user");

graph LR
    A[Client Request] --> B[Server checks Session ID]
    B --> C[Session exists?]
    C -->|Yes| D[Use existing session]
    C -->|No| E[Create new session]
    D --> F[Process Request]
    E --> F

• Purpose: Maintain state across HTTP requests
• HttpSession: Most commonly used method

Mnemonic: “CUHH = Cookies URL Hidden HttpSession”

Question 4(a) [3 marks]

#

Explain architecture of JSP with diagram.

Answer:

JSP Architecture:

graph LR
    A[JSP Page] --> B[JSP Engine/Container]
    B --> C[Servlet Code Generated]
    C --> D[Compiled to Bytecode]
    D --> E[Servlet Executed]
    E --> F[HTML Response]

Mnemonic: “JSP = Java Server Pages (Page to Servlet)”

Question 4(b) [4 marks]

#

Explain JSP scripting elements with example.

Answer:

JSP Scripting Elements:

Examples:

<%! int count = 0; %>               <!-- Declaration -->
<% count++; %>                      <!-- Scriptlet -->
<%= "Count: " + count %>            <!-- Expression -->

Mnemonic: “SED = Scriptlet Expression Declaration”

Question 4(c) [7 marks]

#

Explain JSP life cycle.

Answer:

JSP Life Cycle Phases:

graph LR
    A[JSP Page Created] --> B[Translation to Servlet]
    B --> C[Servlet Compilation]
    C --> D[Class Loading]
    D --> E[Instantiation]
    E --> F[jspInit called]
    F --> G[_jspService handles requests]
    G --> G
    G --> H[jspDestroy called]

• Container Managed: Web container handles entire lifecycle
• Automatic: Translation and compilation happen automatically

Mnemonic: “TCLIIRD = Translation Compilation Loading Instantiation Init Request Destroy”

Question 4(a OR) [3 marks]

#

Explain difference between JSP and Servlet.

Answer:

Mnemonic: “HTML vs Java = JSP vs Servlet”

Question 4(b OR) [4 marks]

#

List out and Explain advantage of JSP.

Answer:

JSP Advantages:

• Developer Friendly: Web designers can work with JSP easily
• Maintenance: Easier to modify than servlets

Mnemonic: “EAPSR = Easy Automatic Platform Separation Reusable”

Question 4(c OR) [7 marks]

#

What is cookie? Explain how to Read and delete cookie using JSP page.

Answer:

Cookie Overview: Cookie is a small piece of data stored on client’s browser to maintain state.

Cookie Operations:

Reading Cookie Example:

<%
Cookie[] cookies = request.getCookies();
if (cookies != null) {
    for (Cookie cookie : cookies) {
        if ("username".equals(cookie.getName())) {
            out.println("User: " + cookie.getValue());
        }
    }
}
%>

Deleting Cookie Example:

<%
Cookie cookie = new Cookie("username", "");
cookie.setMaxAge(0);
response.addCookie(cookie);
%>

Mnemonic: “CARD = Create Add Read Delete”

Question 5(a) [3 marks]

#

Explain importance of MVC architecture.

Answer:

MVC Importance:

• Code Organization: Better structure and organization
• Team Development: Multiple developers can work simultaneously

Mnemonic: “SMT = Separation Maintainability Testability”

Question 5(b) [4 marks]

#

Explain Aspect oriented programming and dependency injection in brief.

Answer:

Aspect Oriented Programming (AOP):

Dependency Injection (DI):

Mnemonic: “AOP = Aspects Over Points, DI = Dependencies Injected”

Question 5(c) [7 marks]

#

Explain MVC architecture.

Answer:

MVC Components:

graph LR
    A[View<br/>Presentation Layer] 
    B[Controller<br/>Control Layer] 
    C[Model<br/>Business Logic]
    
    A --> B
    B --> C
    C --> B
    B --> A

MVC Flow:

1. User Request → Controller receives request
2. Controller → Processes request, calls Model
3. Model → Performs business logic, returns data
4. Controller → Selects appropriate View
5. View → Renders response to user

Advantages:

• Maintainability: Clear separation of responsibilities
• Reusability: Components can be reused
• Testability: Each layer can be tested independently

Mnemonic: “MVC = Model View Controller (Business UI Control)”

Question 5(a OR) [3 marks]

#

Explain advantages of MVC architecture.

Answer:

MVC Advantages:

Mnemonic: “CPEM = Code Parallel Easy Maintenance”

Question 5(b OR) [4 marks]

#

Explain difference between spring and spring boot.

Answer:

• Spring: Comprehensive framework requiring configuration
• Spring Boot: Convention over configuration approach

Mnemonic: “Manual vs Auto = Spring vs SpringBoot”

Question 5(c OR) [7 marks]

#

Explain architecture of Spring framework.

Answer:

Spring Framework Architecture:

graph TD
    A[Core Container<br/>IoC & DI] 
    B[Data Access<br/>JDBC, ORM] 
    C[Web Layer<br/>MVC, WebFlux]
    D[AOP<br/>Aspect Oriented]
    E[Test<br/>Testing Support]
    
    A --> B
    A --> C
    A --> D
    A --> E

Spring Modules:

Key Features:

• IoC Container: Manages object creation and dependencies
• AOP Support: Cross-cutting concerns handling
• Transaction Management: Declarative transaction support
• MVC Framework: Web application development

Mnemonic: “CDWAST = Core Data Web AOP Security Test”