Preface
Recently I just decided to design and impl an object mapping lib that lands between HTTP and POJOs.
You may think of a ORM, that works as wrapper between a data source and POJOs, so that's the same thing actually, but for HTTP.
Later then I decided to make it opensource, becasue why not!
WAsys_pojo_http_data
Inroducing WAsys_pojo_http_data
diagram 0: WAsys_pojo_http_data
lib
WAsys_pojo_http_data
is more like a specification, rather than an implementation, however it has a default POJO parsing, and filling modules that any HTTP Component Module(as data provider) could utilize them.
Component Structure
diagram 1: component structure diagram
WAsys_pojo_http_data
defines a proper/std way between a server(data provider) and user. You may think such a JSR for instance.
For make it run, a HTTP Server should implement the Request_Data_Handler
as data provider.
User should just need to provides hers/his POJOs as Fillable_Object
, and the way target HTTP Server component provides its filling API.
WAsys_pojo_http_data_servlet3_wrapper
As mentioned, WAsys_pojo_http_data
needs to be implemented using a 3rd. party HTTP Server, so I came up with WAsys_pojo_http_data_servlet3_wrapper
that wrap Servlet 3.0
API for WAsys_pojo_http_data
.
WAsys_pojo_http_data_servlet3_wrapper
could be used for any server that supports the Servlet 3.0
API, let say Apache Tomcat.
Where To Start?
Both projects, are available from github.
WAsys_pojo_http_data
| git clone https://github.com/911992/WAsys_pojo_http_data.gitWAsys_pojo_http_data_servlet3_wrapper
| git clone https://github.com/911992/WAsys_pojo_http_data_servlet3_wrapper.git
The compiled artifacts could be grabbed from Central maven repository too, please check repos for dependencies.
More Help? Meta?
Both repo has some sample usage, and very common FAQ/troubleshooting section. Feel free to open any ticket, issue, etc... we regularly check repos, and value quality of the work.