Spring MVC Package Structure

SimonTemplar

Is there any convention about how to structure packages in a Spring MVC application. Should I structure them based on the system’s logically separate business units or based on the Spring MVC architecture.

For example, this (logically separate business units):

com.mycompany.myapp.product
- Product
- ProductDao
- ProductService
- ProductController
com.mycompany.myapp.user
- User
- UserDao
- UserService
- UserController
com.mycompany.myapp.review
- Review
- ReviewDao
- ReviewService
- ReviewController


Or this (Spring MVC architecture)

com.mycompany.myapp.beans
- Product
- User
- Review
com.mycompany.myapp.dao
- ProductDao
- UserDao
- ReviewDao
com.mycompany.myapp.service
- ProductService
- UserService
- ReviewService
com.mycompany.myapp.controller
- ProductController
- UserController
- ReviewController


Thanks

TrueDub

I would always use your second approach, and separate by function. You can then reflect different usages in the sub-package name, if required, or even in the class name.

ChRoMe

The second approach without a doubt.