Description of Issue

The security model is lacking, there are no user groups or group ownership, just levels.

Related Research(if it exists)

The security model is lacking, sharing is impossible.

Proposed Solution(if it exists)

Implement group ownership/access to objects, for read and list operations, and preserve write operations for the owner and admin.

Change the way entities and persistence behave so that users can only access entities associated with them.

Description of Issue

Checking in connections is causing a time delay because we need to check its validity

Related Research(if it exists)

Testing response time with check in validity checks on database threads shows a huge (50ms at least ) increase in response time

Proposed Solution(if it exists)

implement a thread pool and functions to clean up and release resources without blocking execution.

Description of Issue

Doing an authorised update operation causes a 404 error regardless of values

Look into creating a query language that deals with objects rather than SQL, to allow the creation of custom queries without writing SQL code.

Description of Issue

If i have 150 objects, i should have indexes 0-149. Instead, I have indexes matching the id of the object. This is not standard or logical.

Description of Issue

Posting to the test implementation with authorisation results in an error 400 regardless of the data

The current method of connecting to the database(using a singleton class and 1 single thread that dies after a while) is not good enough, nor performing well, and is causing the service to seem down when in fact its just that the thread has not been created yet.

A solution to this would be to implement a database connection pool, which either creates or reuses connections on demand.

Description of Issue

Tokens are passed with the JSON data. This is a ridiculous way to work.

Proposed Solution(if it exists)

Separate them.

Description of Issue

Deleting a non-existent entity returns a success message

Proposed Solution(if it exists)

use executeUpdate() instead of execute()

Description of Issue

There is no way to differentiate between a user not being authorised and an object not being found in the database for update and read operations. This is not a good way to go forward

Proposed Solution(if it exists)

We have success responses, failure responses, and null responses. I think i should use them more. For example, a null response for a put operation means the user is not authorized, a fail response means that the object was not found. For reading/listing, null should mean that the object was not found and failure means that the user is not authorized.

Description of Issue

Building and creating projects based on this framework has gotten cumbersome

Related Research(if it exists)

Maven solves dependency fetching

Proposed Solution(if it exists)

Mavenise this project