How gosiadrygala/finalproject works
Project Type and Purpose
• The project is a client–server application built for managing pricing data and user roles – such as administrators, product administrators, and shop managers.
• It leverages a Java client with a rich GUI (FXML-based views, controllers, and view models) while connecting over a network (via RMI) to a server that implements the business logic and data access.
• The structure suggests a clear use of the Model–View–Controller (or ViewModel) pattern on the client side, a Data Access Object (DAO) pattern for database interactions, and a distributed execution model via RMI for networking.
File Structure
• Top-level directories:
• “PriceChecker” (the main project) contains the “src” directory.
• Within “src” you find distinct sub-packages for:
• client: Contains application entry points (PriceCheckerApp.java, RunPriceChecker.java), the client’s model packages (e.g., loginRegisterModel, administratorModel, etc.), core factories and handlers (ClientFactory, ModelFactory, ViewHandler, ViewModelFactory), networking components (Client, RMIClient) and the views (FXML files, controllers, and view models).
• dataaccess: Implements the DAO layer with classes for connecting to a database (DatabaseConnection, various DAO and Manager classes).
• server: Contains the server entry point (RunServer.java), server-side networking (RMIServerManager), and parallel “servermodel” components that mirror the client’s functionality (e.g., administratorServerModel, loginRegisterServerModel, etc.).
• shared: Holds common networking interfaces (ClientCallback, RMIServer) and utility classes (e.g., Product, ProductList, EventType, User).
• Further, there is a “Testing” directory containing similar structure and tests for nearly every core component of the project.
• The “libraries” directory lists external jar dependencies (ControlsFX and PostgreSQL JDBC) that support the UI and database interactions.
• The clear separation of client, server, shared, and tests in the directory structure indicates the use of layered architecture where the client and server have dedicated responsibilities and communicate over RMI.