title: How should a spring MVC presentation layer be structured compared to a Symfony2 app?
body: <p>To better understand what I'm trying to achieve here is an image of a typical <code>Symfony2</code> application with only one bundle and a spring MVC app side by side:</p>
  <p><img src="https://i.stack.imgur.com/kp0BO.jpg" alt="enter image description here" /> <img src="https://i.stack.imgur.com/A4Xk2.png" alt="enter image description here" /></p>
  <p>I know there is a conceptual difference between <code>Symfony2</code> which can be used to build a whole application and Spring MVC which can also be used to build a whole application, but in my case I want it to act as my <strong>presentation layer only</strong>.</p>
  <p>Working with Spring MVC somewhat feels like working with raw bare metal. I prefer an opinionated approach. I want to have something similar to bundles in <code>Symfony2</code> where each bundle houses its controllers, views, forms, templates, configurations, js and css. I want views to be grouped by controller name.</p>
  <p>I want something that houses the configurations for the whole application such as the database or email server in addition to somewhere where I can add layouts for all &quot;bundles&quot;. I want cache and logs folders.</p>
  <p>I know that I can create all of that manually, but I got that feeling that there should be something like a standard folder structure for spring MVC applications.</p>
  <p>I almost sound like I searching for a framework built on top of <code>Spring MVC</code> (maybe this is the solution after all), but maybe I'm having the wrong approach to the whole thing.</p>
  <p>Note: My business logic is housed in separate bounded contexts. The presentation layer is part of the application that will communicate with all these contexts.</p>