Almost exact Around one year ago I decided to use the Java framework Dropwizard for our server application. Since then I read a lot, I learned a lot and I implemented many things.
As the recently published new Dropwizard version required some re-engeneering engineering of our application, I used the opportunity to start all over again from the beginning to strengthen my knowledge about the whole implementation. I want to permanently understand every single detail of it, that's the only way I can extend and document it in a meaningful way. It should also help other people to get involved in the development!.
To In order to be able to include all the technical features decoupled from the Oregami worldprovide my technical progress to the outside world in a useful way, I created a complete new ToDo application which is generic, thus stripped of the whole Oregami context. You know the drill with those to-do's: an incomplete thing with a list of things you have to do features (name, description, state, ...) that still need doing.
Today the generic application contains the following stuff:
- RESTful app based on Dropwizard version 0.7.0
- Dependency Injection with Google Guice
- Hibernate / JPA 2.1 as persistence framework
- HSQLDB as (in memory) database
- "Transaction-per-HTTP-request" with Guice PersistentFilter
- Support for cross-origin resource sharing
- JPA entities with UUIDs as key
- a pattern for accessing and manipulation manipulating entities with HTTP REST calls
(Resource => Service => DAO => entity) - a pattern for ServiceResult objects which contain ServiceErrorMessages (which can later be bound to the corresponding web form fields in the client)
- continuous JUnit tests to assure correct functionality
...