How wameeee/onlineauctions works
Project type and purpose
• This is a Java-based online auction web application (Servlet/JSP) with MyBatis for persistence and MySQL as the database.
• It implements core user functionality (register, login, browse, bid) and admin functionality (manage auctions, users, records).
File structure
• Top-level:
• pom.xml, create_auction.sql, README.md
• src/main/java/.../web – Servlets and filters (AuthFilter, AuctionServlet, UserServlet).
• src/main/java/.../service + impl – Business logic layer.
• src/main/java/.../mapper – MyBatis mapper interfaces & XML in resources.
• src/main/java/.../entity – Domain model (Auction, AuctionUser, AuctionRecord).
• src/main/java/.../util – Utilities (MyBatisUtil, PasswordUtil).
• src/main/webapp – JSP pages, static assets (css, js, images).
• src/main/resources – MyBatis config, Log4j, mapper XML files.
• Pattern: Classic MVC layered architecture (Controller → Service → DAO → DB), deployed in a Tomcat container.
README for additional insights
• Confirms Java8, Servlet/JSP, MyBatis, MySQL, Tomcat9.
• Database tables: auction, auctionUser, auctionRecord.
• Deployment via Maven/Tomcat7 plugin.