Average Aussie Banking System (Swing)

Description:
This project is Swing implementation of the Average Aussie Banking project.  This provides full create, read, update, and delete functionalities for the users of the system.  There is a search feature that searches the database based on id, first name, last name, email, and type including partial “%like%” searches.  It also has a feature to test the REST server.
Current Build:

  1. Third iteration
    • Created the layout of the graphical user interface (GUI) and add all of the components to the layouts.
    • Created a controller class that implements that implements action listener.
    • Add listeners and action events to the appropriate components.
    • Provided the methods that invoke the EJB to provide the required functionality.

Preview:

Source:
https://github.com/jmiddendo/BankingExampleSwingApp
Future Iterations:

  • Add the ability to add a transaction to the system.
  • Add a login to provide security.

Average Aussie Banking System (REST)

Description:
This project is implements a REST server that exposes the entities for the Average Aussie Banking system.  It provides @GET methods to search for users by type, email, and id.  It also provides a @GET method to search transactions by type.
Current Build:

  1. Third Iteration
    • Developed all the entities based on the existing tables in the database.
    • Developed the REST class based on the generated entity classes.
    • Implemented the four Named queries to provide the required functionalities.

Preview:

Source:
Not Listed
Future Iterations:

  • Add security to restrict access to sensitive data.
  • Expose the remaining Named queries.

Average Aussie Banking System (EJB)

Description:
This project is the implementation of the remote interfaces to provide session beans for the Average Aussie Banking System.  This means that this project contains class that implement all of the business logic for the system.  It also uses a container managed entity manager to implement persistence.
Current Build:

  1. First Iteration
    • Implements a @Remote EJB that manages the BankingTransaction entities in the databases.
    • Adds functionality the provides create, read, user, and delete functionality to the class.
    • Provides search functionalities.
  2. Second Iteration
    • Implements @Remote EJB for BankUser and Account entities with full CRUD and search capabilities.
  3. Third Iteration
    • Creates an EJB to consume the REST server for the system.

Preview:

Source:
https://github.com/jmiddendo/BankingExampleEJB

https://github.com/jmiddendo/BankingExampleCommon
Future Iterations:

  • Add functionality to search by all available attributes.

Average Aussie Banking System (Web Client)

Description:
This project is web application using JavaServer Faces (JSF) to serve as the front-end to the Average Aussie Banking System.  The application provides form-based authentication as the security.  Once authenticated, employees can manage the users in the system.  The customer can update their details and add transactions.
Current Build:

  1. First Iteration
    • Adds functionality to search the transactions by id, name, or type.
  2.  Second Iteration
    • Adds create, read, update, and delete functionality for the BankUser entities.
    • Adds the ability to add a BankTransaction.
    • Add the ability for a customer to update their own profile.
  3. Third Iteration
    • Add form-based authentication using the JAAS API java security.
    • Added the ability to transfer to other customers and not just between their own accounts.
    • Added the ability to search for a user based on id, first name, last name, type, and email using “%like%.”

Preview:

Source:
https://github.com/jmiddendo/BankingExampleWar
Future Iterations:

  • Create an AngularJS implementation for the system.
  • Add the ability to create accounts.

Picture Attribution:

Hotel Broker System Using Java Socket Message Passing

Description:
This project is a hotel broker system that accepts communications from a client.  The client can  request information about what area and hotels the broker services and submit booking information.  The broker accepts the request and queries the appropriate hotel to process the request.  The hotel communicates with the database and responds to the broker.  The broker returns the response back to the client.
Current Build:

  1. First Iteration
    • Created a protocol to standardize communication between the network tiers.
    • Developed a hotel broker that establishes a socket that listens for a client.
    • Created a client that passes messages to the broker.
  2. Second Iteration
    • Designed a database that houses the database that the broker queries.
  3. Third Iteration
    • Programmed a hotel server that queries the database.
    • Updated the broker to serve as the client for the new hotel server.

Preview:

Source:
https://github.com/jmiddendo/HotelBrokerSocketProject

Future Iterations:

  • Full create, read, update, and delete (CRUD) functionalities for the client.
  • A login to identify the client communicating.
  • Security to protect the payment information.