Project structure for the Hibernate Struts project?

Question

I started developing one blog site based on Hibernate and Struts. I was wondering how to keep the directory and file structure. That is, presentations, a sleeping level of access to the database, controllers and business levels. Any suggestion?

Relationship Swar

Answer 1

I do not think that there is one answer to this question, but here is mine.

For a simple project without strong modularity requirements, I would use one project.

For the project layout itself, I follow the standard Maven layout . For webapp, this usually means something like this:

.
└── src
    ├── main
    │   ├── java            - Application/Library sources
    │   ├── resources       - Application/Library resources
    │   └── webapp          - Web application sources
    │       └── WEB-INF
    └── test
        ├── java            - Test sources
        └── resources       - Test resources

java :

• com.acme.<app>.<module>.web.action
• com.acme.<app>.<module>.web.forms: beans
• com.acme.<app>.<module>.service: -.
• com.acme.<app>.<module>.bo: -
• com.acme.<app>.<module>.dao: DAO
• com.acme.<app>.<module>.dao.hib: Hibernate DAO

<module>.

• Java- ​​?