A simple Java Framework for creating CRUD REST web services using java servlets.
By Tareq Kirresh
A simple Java framework for creating CRUD REST web services using java servlets
License: MIT License
A simple Java Framework for creating CRUD REST web services using java servlets.
By Tareq Kirresh
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.
Building and creating projects based on this framework has gotten cumbersome
Maven solves dependency fetching
Mavenise this project
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.
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
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.
The security model is lacking, there are no user groups or group ownership, just levels.
The security model is lacking, sharing is impossible.
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.
Doing an authorised update operation causes a 404 error regardless of values
Deleting a non-existent entity returns a success message
use executeUpdate() instead of execute()
Posting to the test implementation with authorisation results in an error 400 regardless of the data
Checking in connections is causing a time delay because we need to check its validity
Testing response time with check in validity checks on database threads shows a huge (50ms at least ) increase in response time
implement a thread pool and functions to clean up and release resources without blocking execution.
Tokens are passed with the JSON data. This is a ridiculous way to work.
Separate them.
Look into creating a query language that deals with objects rather than SQL, to allow the creation of custom queries without writing SQL code.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.