Take the 2-minute tour ×  We are building a small application
using different architectural layers such as domain, interface,
infrastructure and application. This follows the Onion DDD
model. Now I am wondering if there is any benefit in splitting
the application into a multimodule maven project. As far as I
can see now it seems to make things more difficult than needed.
The entire application will be deployed as a single WAR file
into a Tomcat container.  share|improve this question What
exactly is more difficult than having a single module? – 
khmarbaise Jul 13 '11 at 8:32 The difficulty to use a consist
Spring applicationContext.xml through all modules. I guess that
i need to create an applicationContext.xml for usage within
Spring for all seperate modules, or am i missing something? – 
Marco Jul 13 '11 at 13:21 You shouldn't need multiple
application contexts. You can have several separate modules, and
only one applicationContext.xml to wire up dependencies from
those modules. –  Lyle Sep 21 '12 at 22:23