How giusyann/enjoyourbooks works
Project type and purpose
• Full-stack Java EE/MVC web application
• Purpose: an e-commerce site for buying books (digital/print), users can publish manuscripts (admin approval), manage wishlists, orders, invoices, reviews.
File structure
• src/main/webapp – all client-facing resources (JSP views, static JS/CSS/images, error pages, index.jsp).
• src/main/java/com/.../control – Servlet controllers handling HTTP requests (e.g., catalogoServlet, checkoutServlet, registrazioneServlet).
• src/main/java/com/.../dao – Data Access Objects (bookDao, orderDao, userDao, etc.).
• src/main/java/com/.../model – Domain beans (bookBean, orderBean, userBean) and DriverManagerConnectionPool.
• src/main/resources/META-INF – beans.xml & persistence.xml for DI/JPA configs.
• External libs in WEB-INF/lib: MySQL connector, Gson (JSON), Protobuf, javax.mvc-api, jQuery.
Key architectural patterns
• MVC (Model – View – Controller) / “Model2” Java EE
• DAO pattern for data persistence
• JDBC (via connection pool) and optional JPA settings
• REST or MVC annotations in HelloResource (JAX-RS or javax.mvc API)
Main components
[Client Browser –> HTTP]
↳ Static assets (JS/CSS) & JSP pages
[Servlet Container / Web Server]
– Controller layer
• Servlets (control/*.java)
• HelloServlet / HelloResource endpoints
– View layer
• JSP templates rendering HTML + EL + JSTL
– Business / Service layer
• Calls to DAO objects
– Data layer
• model/*.java beans
• DriverManagerConnectionPool (JDBC)
• persistence.xml (if JPA used)
[Database]
– MySQL instance (schemas for books, users, orders, reviews, etc.)
[External libraries]
– Gson (JSON serialization for AJAX responses via JSONResponse.java)
– Protobuf (if used for RPC or data exchange)
– jQuery (AJAX on the client)
Relationships and data flow
1. Browser issues an HTTP request (e.g., “/catalogoServlet”).
2. Servlet Container dispatches to the appropriate Servlet.
3. Servlet reads request params, calls DAO(s) for CRUD operations.
4. DAO uses DriverManagerConnectionPool to open JDBC connection → executes SQL against MySQL.
5. DAO returns JavaBean(s) to the Servlet.
6. Servlet places beans in request/session scope, forwards to a JSP.
7. JSP renders HTML + embeds data, returns response.
8. Browser may use jQuery to call JSONResponse endpoints (e.g., for dynamic “add to cart” AJAX), processed by control/JSONResponse.java with Gson.
Architectural principles to highlight
• Separation of concerns – clear layers for view, controller, service/DAO, persistence.
• Reusable DAOs & JavaBeans as model objects.
• Configuration via Maven (pom.xml), beans.xml for DI, persistence.xml for JPA.
• Monolithic deployment – one WAR deployed to any Servlet container (Tomcat/Jetty).
Detailed elements
• Frontend: Browser → JS/CSS → JSP pages (catalog, checkout, login, etc.)
• Controllers: List of major Servlets (catalogoServlet, checkoutServlet, registrazioneServlet, etc.) and HelloResource
• Service/DAO: bookDao, orderDao, recensioneDao, userDao
• Models/Beans: bookBean, orderBean, userBean, recensioneBean
• Persistence: DriverManagerConnectionPool, MySQL schema
• External libs: Gson (for JSONResponse), Protobuf, jQuery, JDBC driver
• Config: beans.xml, persistence.xml, web.xml, pom.xml