This is a REST cinema project that allows users to register and authenticate. It consists of two roles: user and admin, each with specific limitations in terms of project functionalities. For example, the admin can add movies, cinema hall, and movie sessions but does not have access to cart and order-related actions. Users can browse and select movies, view available showtimes, add desired tickets to their cart, and make orders. For a detailed breakdown of role-based capabilities, please refer to the cinema/config/SecurityConfig file.
- User registration and authentication as both user and admin
- Adding movies and displaying all previously added movies
- Adding cinema halls and displaying all previously added halls
- User search by email
- Adding, deleting, updating, and searching for available sessions for a specific movie on a given day
- Adding sessions to the shopping cart and viewing the contents of the cart
- Completing an order and reviewing the order history for each user
The web-application has 3-tier architecture:
- DAO
- Service
- Controller
There are also relations between the tables. The complete database structure is shown below.
- Java 11
- Hibernate
- Spring MVC, Security
- Maven
- MySQL
- Log4j2
- JUnit
- Mockito
- HSQLDB
All possible requests are listed below. In {} are fields for POST, PUT methods that must be filled in the body of the method in the form of JSON format.
And () contains the names of parameters for GET requests.
POST: /register { “email” , “password” , “repeatPassword”}
GET: /users/by-email (email)
GET: /cinema-halls
POST: /cinema-halls {“capacity”, “description”}
GET: /movies
POST: /movies {“ title”, “description”}
GET: /movie-sessions/available (movieId, date MANDATORY FORMAT 13-05-2023)
POST: /movie-sessions { “movieId” , “cinemaHallId” , “showTime” MANDATORY FORMAT 2023-05-13T12:30:00}
PUT: /movie-sessions/{id} { “movieId” , “cinemaHallId” , “showTime” MANDATORY FORMAT 2023-05-13T12:30:00}
DELETE: /movie-sessions/{id}
GET: /orders
POST: /orders/complete
PUT: /shopping-carts/movie-sessions {“movieSessionId”}
GET: /shopping-carts/by-user
- The first step is to configure the database connection. To do this, open the file resources/db.properties and enter the correct data for connecting to your database.
- After that, you need to configure Tomcat (Use only Tomcat 9). To do this, you have to choose
war explodedand leave only/in the application context.
- Before working with this REST application, you will need a request-sending program (such as Postman or similar tools).
Prior to starting and testing the application, you need to configure the request-sending program. I will demonstrate using Postman as an example.
In this project, there is no option to create a user with an
ADMINrole using requests. However, for convenience during project deployment, a user with the loginadmin@i.ua, passwordadmin123and theADMINrole is automatically added to the database(cinema/security/DataInitializer). Therefore, you can use these credentials for authentication. But if you want to register a new user, you can do so using the requesthttp://localhost:8080/register. This is the only request accessible to non-authenticated users. Next, in Postman, you need to go to theAuthorizationtab and selectBasic Auththen enter the appropriate login and password (see the screenshot below). You should perform these steps for all other requests you want to send.
Please note that some requests may be available only to users, while others may be restricted to administrators(refer to cinema/config/SecurityConfig).
