Search code examples
javaspringtomcatcode-organization

Project structure organization: how to make it better?

All -

we have several web applications, all based on some version of Spring developed over time by different team across organizations. They each produce their own WAR, have a different context to work within, and often gets deployed on the same machine, as their functionalities are closely knit together. So we end up with:

tomcat/webapps/{A, B, C ... }

upon deployment, each use a very similar set of tool chains, replicate all Spring jars and dependencies all around.

I am wondering if there is a way to make the project structure better, deploy as a SINGLE war, while allowing each webapp live in their own source repo and have its own pace of development??

Any pointer or references are much appreciated.

Oliver

Solution

  • you would have to probably move to an app server like jboss, but couldn't you use an ear file and have maven build the modules for you? That way you could probably put them in separate repos if you want each with it's own pom and then have another project with a pom for the ear file:

    here is the maven ear plugin:

    http://maven.apache.org/plugins/maven-ear-plugin/

    here is an older blog post about multiple spring app ear file (single applicationContext fo all wars to share if you need):

    http://blog.springsource.com/2007/06/11/using-a-shared-parent-application-context-in-a-multi-war-spring-application/