How itsjupiter000/meditrack works
Project type and purpose
• Project type: Java EE web application (Servlet-based full-stack web app).
• Purpose: MediTrack is an online medicine management system that lets users add, update, delete, and display medicine records per patient. It uses Java Servlets for backend logic, HTML/CSS for the UI, MySQL for persistence, and runs in a Tomcat container.
File structure
• Top-level directories/files:
• src/main/java – Servlet classes and data-access code
• src/main/webapp – Static HTML pages, WEB-INF (web.xml, libraries)
• build/classes – Compiled .class files
• README.md – High-level project description and tech stack
• In src/main/java:
• Home.java, Display.java, AddMedicine.java, UpdateMedicine.java, DeleteMedicine.java – act as Controllers
• DBHandler.java – data-access object (DAO) using JDBC
• Medicines.java – model/entity class
• In src/main/webapp:
• HTML pages mapped to each servlet action
• WEB-INF/web.xml – servlet mappings, context params
• WEB-INF/lib/mysql-connector-j.jar – JDBC driver
README for additional insights
• Confirms MVC-style separation: HTML views, Servlets as controllers, DBHandler+MySQL as model/persistence.
• Technical stack: Java Servlets, MySQL, HTML/CSS, Tomcat, JDBC.
Detail and coverage
• Servlet mappings (from web.xml) if desired.
• Medicines entity class bridging DB rows ↔ Java objects.
• Call out the JDBC driver as a dependency in WEB-INF/lib.
• CRUD operations as separate flows or annotate the Add/Update/Delete/Display paths.
• Be explicit about configuration files (web.xml) and where they reside in the deployment.