Web application for Teaching Assistant (TA) recruitment at BUPT International School. TAs browse vacancies and submit applications; Module Organisers (MOs) post jobs and review applicants; Administrators manage users, workload, password resets, audit logs, and system settings.

Built for EBU6304 coursework: Java only, no database (JSON file storage), Agile delivery.

This README provides instructions for setting up, configuring, and running the software.

Verify Java is installed:

java -version
javac -version

Clone or download this repository, then open a terminal in the project root:

Software_Group_54/Test_Version_02/

All commands below must be run from this folder. The server uses the current working directory as the project root for data/ and uploads/.

The project uses one external library:

On first build, build.bat downloads Gson from Maven Central if the JAR is not present.

Optional (for unit tests only):

No Maven, Gradle, Node.js, or database installation is required.

Windows — PowerShell (recommended):

.\build.bat

In PowerShell, scripts in the current folder must be invoked with the .\ prefix. In CMD, you can also run build.bat without the prefix.

This compiles Java sources into out/ and creates data/ and uploads/ at runtime when the server starts.

macOS / Linux (manual equivalent):

mkdir -p out lib
# Download gson-2.10.1.jar into lib/ if missing
javac -encoding UTF-8 -cp "lib/gson-2.10.1.jar" -d out \
  src/main/java/com/bupt/tarecruit/model/*.java \
  src/main/java/com/bupt/tarecruit/service/*.java \
  src/main/java/com/bupt/tarecruit/handler/*.java \
  src/main/java/com/bupt/tarecruit/Main.java

If the build fails, confirm javac is on your PATH and rerun the build command.

Default HTTP port is 8080. Change it when starting the server:

.\run.bat 9090

Or run Java directly:

java -cp "out;lib\gson-2.10.1.jar" com.bupt.tarecruit.Main 9090

On macOS/Linux, use : instead of ; in the classpath.

Runtime configuration is stored in data/settings.json. The file is read on startup and can be updated through the Admin portal or by editing the file while the server is stopped.

Common settings:

Admin UI: log in as Admin → System Settings (/admin/system-settings.html) → adjust recruitment period, max weekly hours, SMTP, and email templates → Save All Changes.

When an administrator approves or rejects a password-reset request, the system can send notification email via SMTP. Mail is optional; core features work without it.

Configure using either environment variables or data/settings.json keys (server restart or Admin save required):

Example (settings.json fragment — replace with your own credentials):

{
  "mail.smtp.host": "smtp.example.com",
  "mail.smtp.port": "465",
  "mail.smtp.username": "your-account@example.com",
  "mail.smtp.password": "your-smtp-auth-code",
  "mail.smtp.from": "your-account@example.com",
  "mail.smtp.fromName": "TA Recruit Support"
}

Do not commit real SMTP passwords to version control.

Both directories are created automatically on first run. To reset the environment to a clean state:

1. Stop the server (Ctrl+C).
2. Delete the data/ and uploads/ folders (or rename them as backup).
3. Restart the server — default admin and demo seed data will be recreated.

Windows — PowerShell:

.\run.bat

Custom port:

.\run.bat 9090

macOS / Linux:

java -cp "out:lib/gson-2.10.1.jar" com.bupt.tarecruit.Main

Expected console output:

  TA Recruitment System v2
  Running at http://localhost:8080
  Default admin: admin / admin123

Stop the server with Ctrl+C.

After the server starts, open these URLs in a browser (replace 8080 if you used a custom port):

The backend serves static HTML from TA/, MO/, and admin/, and REST APIs under /api/.

On first run, data/users.json is created with a default administrator and seeded demo accounts.

Seeded TA student IDs (password 123456 for all):

New TA and MO accounts can also be registered from their respective login pages.

1. MO logs in → creates or manages job postings → reviews and approves/rejects applications.
2. TA logs in → browses open jobs → submits application (with optional CV upload and draft save).
3. Admin logs in → monitors workload and statistics → manages users → processes password-reset requests → exports data.

Key management pages auto-refresh periodically when the browser tab is visible, so multi-user demos update without manual reload.

Unit tests use JUnit 5 and do not require the HTTP server to be running. Full commands and expected output (103 tests successful) are documented in Test_Version_02/UNIT_TEST_EVIDENCE.md.

Quick summary from the project root (PowerShell on Windows):

javac -encoding UTF-8 -cp "lib\gson-2.10.1.jar" -d out src\main\java\com\bupt\tarecruit\model\*.java src\main\java\com\bupt\tarecruit\service\*.java src\main\java\com\bupt\tarecruit\handler\*.java src\main\java\com\bupt\tarecruit\Main.java

javac -encoding UTF-8 -cp "lib\gson-2.10.1.jar;lib\junit-platform-console-standalone-1.10.2.jar;out" -d out src\main\java\com\bupt\tarecruit\unit_testing\*.java

java -jar lib\junit-platform-console-standalone-1.10.2.jar --class-path "out;lib\gson-2.10.1.jar" --scan-class-path

Test_Version_02/
├── build.bat / run.bat          # Build and run scripts (Windows)
├── lib/                         # gson-2.10.1.jar (+ JUnit jar for tests)
├── out/                         # Compiled Java classes (created by build)
├── data/                        # JSON data files (runtime)
├── uploads/                     # Uploaded files (runtime)
├── src/main/java/com/bupt/tarecruit/
│   ├── Main.java                # HTTP server entry point
│   ├── model/                   # Data models
│   ├── service/                 # DataService, MailService, AiMatchingService
│   ├── handler/                 # REST API handlers
│   └── unit_testing/            # JUnit 5 tests
├── TA/                          # TA applicant frontend
├── MO/                          # Module Organiser frontend
├── admin/                       # Administrator frontend
└── js/api.js                    # Shared frontend API helper

• Standalone Java with embedded com.sun.net.httpserver.HttpServer (no Spring Boot).
• File-based JSON storage (no SQL database).
• Three role-based web portals (TA, MO, Admin) with REST API backend.
• Supports iterative Agile delivery with traceable user stories.

For module-specific UI notes, see Test_Version_02/TA/README.md, Test_Version_02/MO/README.md, and Test_Version_02/admin/README.md.