How armybit/bankapp works
Project Type and Purpose
• This is a full-stack Java web application (“Bank App”) that provides user authentication, account balance look-up, and operation history.
• It uses Jakarta EE servlets as the controller layer, JSP pages as the view layer, a DAO pattern for persistence, and a relational database (bank.sql) as the data store.
File Structure Analysis
• Top-level: pom.xml (Maven build), bank.sql (DDL/DML), src/main (code & web assets).
• src/main/java/com/bankapp/bank:
• dao & daoImp: interfaces + implementations for CRUD on users, accounts, operations.
• db: DatabaseConnectionManager (manages JDBC connections).
• model: POJOs for User, Account, Operation entities.
• servlet/authentification: servlets handling login, signup, dashboard, internal/external ops, commissions.
• src/main/webapp:
• JSP views under /login and /dashboard.
• web.xml for servlet mappings.
Key Architectural Patterns
• MVC:
• Model = model package + bank.sql schema
• View = JSP pages
• Controller = servlets
• DAO Pattern for persistence isolation.
• Single-node monolith deployed on Tomcat 10.
Main Components
A. Web Client (Browser)
• Interacts via HTTP/HTTPS with the Tomcat server.
B. Web Server (Tomcat 10)
• Hosts:
• Servlets (/authentification/*)
• JSPs (/login, /dashboard)
C. Controller Layer (Servlets)
• Entry points: auth.java, Signup.java, dashboard.java, Commission.java, OpsInterne.java, opsExterne.java
• Handles HTTP requests, session management, routes to views.
D. Service/Business Logic (could be thin or embedded in servlets)
• For balance retrieval, operation listing, commission calculation.
E. DAO Layer
• dao interfaces + daoImp implementations
• CRUD operations on User, Account, Operation entities.
F. Database
• MySQL/PostgreSQL (represented by bank.sql)
• Tables: users, accounts, operations, commissions
Relationships and Data Flows
• Browser → HTTP → Tomcat/Servlet Container
• Servlet receives request → invokes DAO via DatabaseConnectionManager → executes SQL on DB → returns model objects → forwards to JSP → HTTP response to browser.
• Bi-directional on DAO ↔ Database (queries, results).
Technologies and Frameworks
• Java 20, Jakarta EE Servlets, JSP, JDBC
• Tomcat 10
• Maven for build & dependency management
• Rectangles for components (Servlets, DAO, DB)
• Blue = Presentation (JSP, Servlets)
• Green = Business/DAO
• Orange = Database