COLLABORATIVE JAKARTA EE PROJECT
A server-rendered Jakarta EE application for authenticated access, customer records, tablet and smartwatch inventory, and stock-aware order processing.
I implemented Jakarta Faces presentation components, backing beans, the authenticated-page filter and the local email service that connect user workflows to the team’s EJB and persistence layers. I also refined the interface and corrected customer-profile navigation.
SmartTech was developed collaboratively for COIT20259 Applied Distributed Systems. My work focused on the presentation layer, authentication-related integration, local email delivery, customer navigation and interface consistency.
01 / CONTEXT
SmartTech connects customer records, two product categories and customer orders while keeping presentation, business and persistence responsibilities in separate application tiers.
A technology retailer needs customer information, product stock and order activity to work together. An order should refer to an existing customer and product, and it should not be created when the recorded stock is insufficient.
The internal management pages also require an authenticated session instead of relying only on hidden navigation links.
Customer, product and order data need to operate as connected workflows rather than isolated forms.
Order creation checks recorded availability and updates the selected product quantity.
A servlet filter redirects unauthenticated requests away from internal management routes.
Jakarta Faces pages, EJB services and JPA entities must exchange data across a collaborative codebase.
02 / SYSTEM SCOPE
The application is an internal retail-management workspace rather than a customer-facing online store.
Create, list and search tablet records while storing device specifications and stock quantities.
Create, list and search smartwatch records with wearable attributes and stock information.
Create customer profiles, search contact information and open the selected customer by ID.
Select a customer and product, create an order and update the recorded product quantity.
03 / ARCHITECTURE
Jakarta Faces handles server-rendered pages and form interaction. Presentation beans call stateless EJB services, while Jakarta Persistence connects those services to MySQL through a JTA data source.
mvn clean verify with Java 11 on pushes and pull requests to main.04 / MY CONTRIBUTION
My work covered the application screens and the Java classes that prepare data for those screens, handle authentication-related navigation and connect user actions to the business tier.
I also implemented local email delivery for verification and recovery codes, corrected customer-profile routing and applied consistent responsive styling across the application.
Implemented the Jakarta Faces backing bean and pages for registration, verification, login, account recovery, password reset and logout.
Added a servlet filter that allows public pages and static resources while redirecting unauthenticated management requests to the login page.
Connected customer, tablet, smartwatch and order forms, tables and search views to the team’s business services.
Implemented Jakarta Mail delivery for account-verification and recovery codes through a local FakeSMTP server.
Updated list and search links to pass the selected customer ID and load the matching profile record.
Applied shared SmartTech branding, responsive layouts, navigation and feedback patterns across authentication and management pages.
05 / IMPLEMENTATION EVIDENCE
The following workflows show where the interface connects to application services and stored data.
The login filter distinguishes public pages and static resources from internal routes. Requests without an authenticated session are redirected to the login page.
Registration, verification, login, recovery and password reset move through the authentication bean, account service, persisted account state and Jakarta Mail service.
The order service calls the product service to deduct stock before persisting an order. Deleting the order restores the recorded quantity before the order is removed.
06 / ORDER WORKFLOW
The sequence connects a Jakarta Faces form to customer, product and order services.
The form loads options from persisted customer records.
An AJAX update refreshes the product options for tablets or smartwatches.
The backing bean parses the selected IDs and quantity, then creates an order object.
The product service confirms that the current stock is at least the requested quantity.
The stock value is changed before the order is persisted by the business service.
Deleting an order returns its quantity to the referenced product before removing the order record.
07 / INTERFACE AND DATA
The public repository includes application screenshots and the local MySQL schema used by the academic build.
08 / APPLICATION IMPROVEMENTS
The original application functions were retained while the interface, navigation and public setup information were improved.
09 / OUTCOME
SmartTech demonstrates work in a layered Java web application: implementing server-rendered interfaces, connecting them to business services, managing authenticated sessions and coordinating customer, product and order data.
Presentation, business and persistence responsibilities are separated in the codebase.
Customers, products, orders and stock changes operate through the same application.
Public account pages and session-protected management routes form one account flow.
The repository preserves the team history while documenting my implementation areas.
10 / CURRENT SCOPE
The application is complete for its academic scope. The following items would need attention before broader deployment.
java.util.Random and the account model has no expiry or attempt-limit fields.The repository contains the collaborative application, screenshots, local environment guide and Maven workflow. Commit history remains available for reviewing team contributions.
Explore the repository ↗CASE STUDY 04