J2EE Examination Study Notes

J2EE Examination Study Notes

• Subject Code: 2035001
• Faculty Code: 003
• Time: 2½ Hours
• Total Marks: 70

Question 1

• (a) One or Two Word Answers:

  • Web Server: A software application that serves web pages to users.
  • Session: A temporary communication established between a user and a web server, typically used to maintain a user's state across multiple requests.
  • Java Messaging Service (JMS): A messaging standard for Java applications, enabling asynchronous communication between applications.
  • Java Database Connectivity (JDBC): An API that provides a standard way for Java programs to access and manipulate databases.

• (b) Attempt Following (Any 1):

  • Explain Tomcat: It is a widely used, open-source web server and servlet container, primarily designed for use with Java Servlets and Java Server Pages (JSPs).
  • J2EE Advantages:
    • Platform Independence: J2EE applications can run on any platform that supports the Java Virtual Machine (JVM).
    • Robustness: The J2EE platform provides various features for security, error handling, and transaction management.
    • Scalability: J2EE applications can be easily scaled to handle large numbers of users.

• (c) Answer Following (Any 1):

  • JDBC type-I Driver: This is a bridge driver which establishes a direct connection to the database using the database's own native protocol.
  • Connection String: A string that contains all necessary information for a Java program to connect to a specific database.

• (d) Answer in Detail (Any 1):

  • JDBC Drivers:

    • Type 1 (JDBC-ODBC Bridge): Uses ODBC (Open Database Connectivity) to connect to a database, relying on the database's own ODBC driver.
    • Type 2 (Native API Partly Java Driver): Uses a combination of Java code and the database's native API libraries.
    • Type 3 (Net-Protocol Driver): Uses a network protocol to communicate with a database server.
    • Type 4 (Pure Java Driver): Completely written in Java, interacting directly with the database server using its native protocol.

  • Enterprise Architecture Styles:

    • Layered Architecture: Separates application functionality into distinct layers (e.g., presentation, business, data access) to enhance modularity and maintainability.
    • Microservices Architecture: Divides a large application into smaller, independent services that communicate with each other using APIs.
    • Event-Driven Architecture: Involves asynchronous communication based on events, enabling loose coupling and scalability.

Question 2

• (a) One or Two Word Answers:

  • Java Naming and Directory Interface (JNDI): A standard API for accessing and managing directory services.
  • Remote Method Invocation (RMI): Allows objects on one Java Virtual Machine (JVM) to invoke methods on objects running on another JVM.
  • Servlet: A Java program that extends the functionality of a web server, typically used to handle client requests and generate dynamic web content.
  • Web Deployment Descriptor File (web.xml): A configuration file that contains settings relevant to web applications, such as servlet mappings and deployment parameters.

• (b) Answer Following (Any 1):

  • J2EE APIs (Application Programming Interfaces):

    • Java Servlet API
    • JavaServer Pages (JSP) API
    • Java Message Service (JMS) API
    • Java Transaction API (JTA)
    • Java Naming and Directory Interface (JNDI) API
    • JDBC API

  • request.getParameter(): A method in the Servlet API that retrieves values from HTTP request parameters.

• (c) Answer Following (Any 1):

  • web.xml File: A configuration file used in web applications to define servlets, their mappings to URLs, and other deployment settings.
  • Request vs Response: In web development, a request is sent from a client (e.g., web browser) to a server, while a response is sent back from the server to the client.

• (d) Answer in Detail (Any 1):

  • web.xml File: It is a crucial configuration file used in web applications to define deployment configurations and settings. It contains information about:
    • Servlets: Mapping to specific URLs, initialization parameters, and lifecycle settings.
    • JSP Pages: Configuration for their lifecycle and handling.
    • Filters: For pre-processing and post-processing of requests and responses.
    • Listeners: To receive events that occur within the application.
    • Security Constraints: Defining authorization rules for accessing specific resources.
    • Data Sources: Defining connections to databases.
    • Welcome Files: Specifying default pages to be displayed when visiting the application.