Question

Current project structure

On my first spring mvc project, I am trying to get a better understanding of the directory structure with this project and why it is done as such

I get what goes in ‘controllers’ and ‘views’ directory, but am unsure of the others. If I look at the .java file in beans and commands, they look the same to me – no difference in annotations between the two, so why can’t the 2 directories be combined into one?

What goes into services?

The mappers looks like it is for mapping with a database for an OR/M object

Not sure of resolvers directory

Is this standard way of organizing spring mvc projects?

Answer 1

Every project has its structure according to the style of organization/user. The structures abide the standards set down by the organization. So they vary from one to another. A MVC project can be broadly categoried into

1. controllers
2. services //Business Logic layer. Layer between controller and dao
3. dao // Communicates with DB
4. command or bo or vo (whatever name suits your fancy)

The above are the main three. Then there might be other folders like

1. utils //Converters, validators etc could go here or in their own package
2. resources // Place your .properties, xmls etc here

In the context of spring, any class marked with an annotation inheriting from @Component is a bean, so the structure that you have mentioned in the question could have been made keeping that in mind but isn’t being used correctly.

The resolvers folder might host View Resolvers. This is, again, just a guess. Depends entirely on you.

You could look into maven’s spring archetype and the way it organizes a spring project to get a view of how the creators of Spring organize a project.