Web Application Architecture

[Vikas Kapoor]

This is what I have designed. experts' input/feedback??

    
com.companyname.projectname.modulename.controller // Controllers
                                      .service // Service Classes for business logic
                                      .command // POJOs
                                      .validator // Validator (I'm using Spring Framework so I have created separate directory for it)
com.companyname.projectname.persistence // Classes to communicate with hibernate and hence to the database i.e. DAO
                           .secuirty // Application security related stuff like Spring security classses, user authentication, password recovery etc.
                           .util // Utility Methods
resources.hibernate // Hibernate Mapping Files (.hbm.xml)
resources.localization // Property files
resources.spring // Spring Configuration files
//(Everything above will go into src that is source directory)

Where the stuff like Jsps,Images and JavaScript would go? Under WEB-INF?

[Bear Bibeault]

Why do all the packages not start with com.companyname.projectname?

Vishal Pandya wrote:Where the stuff like Jsps,Images and JavaScript would go? Under WEB-INF?

If your app is properly structured such that all requests go through servlet controllers, the under WEB-INF is a great place for the JSPs. That ensures that they cannot be directly addressed.

Images and JavaScript on the other hand, must be addressable by URL and cannot go under WEB-INF.

[Vikas Kapoor]

Bear Bibeault wrote:Why do all the packages not start with com.companyname.projectname?

Do you mean resources should also be start with com.companyname.projectname?

[Bear Bibeault]

Are they on the classpath?

[Vikas Kapoor]

Bear Bibeault wrote:Are they on the classpath?

Doesn't the whole source directory go to classpath? I didn't get you?

[Bear Bibeault]

Vishal Pandya wrote:

Bear Bibeault wrote:Are they on the classpath?

Doesn't the whole source directory go to classpath?

No, sources shouldn't even be part of the web app. The class files (along with the properties files) go on the classpath.

But with regards to the resources... The purpose of the package structure is to prevent naming collisions. By prefixing the packages with com.whatever.thisnthat you prevent collisions. What is preventing collisions for your resources?

[Vikas Kapoor]

No, sources shouldn't even be part of the web app. The class files (along with the properties files) go on the classpath.

Yeah, I mean to convey that only. The whole resources package would be on classpath.

What is preventing collisions for your resources?

Ok, I got your point. So resources too start with com.whatever.thisandthat.

The purpose of the package structure is to prevent naming collisions.

Indeed.

Everything else is ok?

[Vikas Kapoor]

Thanks Bear!