An Head End Application that allows to store Bank Account transactions and allows to make analysis
This part is the Head End part and exposes the data via RESTful services
Project set up and CI&CD life cycle
GET /BankAccounts/
GET /BankAccounts/{id}
GET /BankAccounts/{id}/transactions/
GET /BankAccounts/{id}/transactions/{id}
from a relational db (MariaDB)
POST /BankAccounts/
POST /BankAccounts/{id}
POST /BankAccounts/{id}/transactions/
POST /BankAccounts/{id}/transactions/{id}
from a relational db (MariaDB)
PUT /BankAccounts/
PUT /BankAccounts/{id}
PUT /BankAccounts/{id}/transactions/
PUT /BankAccounts/{id}/transactions/{id}
from a relational db (MariaDB)
mvn -U -X -Pall-tests,local-depl-j2se-h2 clean install
mvn -U -amd -pl ba-services/ba-services-rest-impl-jaxrs/ -Pall-tests,local-depl-j2se-h2 jetty:run
java -jar ~/.m2/repository/com/h2database/
export BANKANALYZER_SRC_HOME=/path_to/bankanalyzer-he export JETTY_HOME=/path_to_jetty/
cp
OAUTH2 flow is called authorization Code and it involves 3 parties:
- the end user,
- the 3rd party service (called client)
- the resource server that is protected by the OAUTH2 filters
Workflow Typically a client offers a service feature that an end user requests. The service feature requires the end user to access one or more protected resources on behalf of this user which are located at the resource server.