Your task is to build a JEE web application that uses Enterprise JavaBeans (EJB) and Java Persistence API (JPA) to manage the persistence of Java objects to a relational database. The application should allow users to create, read, update, and delete records from the database using a web interface. Requirements 1. The application should have a simple user interface that allows the user to view a list of records from the database, add new records, update existing records, and delete records. 2. The application should use EJB to manage the business logic of the application, including the management of transactions and persistence of entities to the database. 3. The application should use JPA to persist Java objects to a relational database. You should use one of the supported JPA implementations, such as Hibernate or Eclipse Link. 4. The application should use a database schema that is compatible with the JPA entity classes used by the application. 5. The application should use a database connection pool to manage connections to the database. You should configure the connection pool using the JEE container's built-in support for connection pooling. 6. The application should handle errors gracefully and provide informative error messages to the user. 7. The application should be deployed to an Azure web app, and should be accessible from a web browser. 8. You should create a video demonstrating the functionality of your application. The video should show how to access the application, Submission You should submit your application as a ZIP file containing the source code, build files, and any other resources necessary to build and deploy the application. You should also include a README file that provides instructions on how to build and deploy the application, as well as any other information that may be useful for the grader. Your application will be graded on the following criteria: Functionality: Does the application meet the requirements outlined in the assignment? Design: Is the application well-designed and easy to understand? Code Quality: Is the code well-structured, well-documented, and easy to read? Deployment: Does the application deploy and run successfully on Azure? . . . .