❗ This repo was used for learning purposes. It is definitely NOT production ready. It is probably NOT well designed. It is certainly NOT bug-free 😄 Use it at your own risk ❗
Todolist MVC is like TodoMVC but for Java Web Frameworks instead of Javascript Frameworks.
The goal is to implement the same application using different technologies and compare them in order to help you choose the right framework for your next Java web application.
Two types of frameworks are being compared:
- Servlets/JSPs
- Spring MVC
- Struts
- JSR 371 Java EE 8 MVC 1.0 (WIP)
- Tapestry
- JSF
Other frameworks will be added progressively (JSR 371, Wicket, Grails, Play, etc..), you are welcome to contribute with any Java web framework you are comfortable with.
Performance comparison is not addressed here. There are many excellent benchmarks on the web like TechEmpower's Framework Benchmarks.
The goal is to focus on features set and developer productivity using each framework:
- Form handling
- Request parameters binding
- Session handling
- Ajax support
- I18N support
- etc
Todolist MVC is the classic CRUD web application to manage todo list online.
Some features like user and session management go beyond CRUD operations. The application is small enough to be easy to implement, and big enough to cover most of the features of each framework. Here is the list of features:
- Register a new account
- View account details
- Update account
- Delete account
- Login
- Logout
- CRUD operations on todos
- Search todo list
Todolist MVC uses Twitter Bootstrap for the user interface, here are some screenshots:
The application's backend is developed using Spring and JPA/Hibernate. Data is persisted in an in-memory HSQL database to make testing/running the application relatively easy.
The module named todolist-core is common to all web layers and is a good use case to see how web frameworks integrate with Spring.
Common web utilities (JSTL tags, Filters, Backing beans, etc) are packaged in a separate common web module named todolist-web-common.
For each web framework, a separate war module is created to implement ONLY the web layer of the application.
View technology may vary for each framework. Here, JSP views are (re)used for most of current implementations. Thymeleaf is also planned to be used as alternative to JSPs.
URLs under /user/* and /todos/* must be accessible to only logged users.
This requirement should be implemented using a servlet filter or equivalent (Struts interceptor, Spring MVC interceptor, etc)
Note that security is not addressed since not all frameworks provide security support.
Form validation should be done using Bean Validation API (JSR303). Form backing beans are already defined with validation constraints in the todolist-web-common module.
All you have to do is to integrate the validation logic with the framework in use.
Finally, the static html template located in src/site/template can be used as a starting point to implement the application with a new framework.
- Check out the project source code from github :
git clone https://github.com/benas/todolist-mvc.git - Open a terminal and run the following command from root directory :
mvn install - Choose a web framework to test and run it. For example :
cd todolist-web-springmvc && mvn tomcat7:run - Browse the following URL :
localhost:8080/ - You can register a new account or login using the following credentials : foo@bar.org / foobar
In order to compare these frameworks objectively, the best implementation should be provided for each framework.
If you are an expert in some of these technologies, please don't hesitate to fix/improve every single aspect of the current implementation.
The goal of Todolist MVC is to be community driven, so every single contribution is welcome!
- Add Spring boot support
- Add JSR 371 (Ozark) implementation
- Add Thymeleaf support
- Update static resources (Bootstrap, FontAwesome) to last versions
- Update dependencies to last versions
- Add comparsion table
Todolist MVC is released under the MIT License.