title: Java Web Project Structure Best Practice
body: <p>I am starting a new Java Web Project which is using Hibernate and a standard MVC Architecture. 
  I have just started to layout the projects structure and while doing this I started to look around to see if there was any standards in this area, about where Controllers should go and generally the best way to lay everything out. However I have not really found any guidelines.</p>
  
  <p>So what I am curious to know is</p>
  
  <ul>
  <li>Is anyone aware of any best practise guidelines for the layout of a Java Web Project?</li>
  <li>Does anyone have a particular set of hard rules that they always follow for different types of project?</li>
  <li>Do people tend to split packages by the different layers such as presentation, business, and application?</li>
  </ul>