Web project architecture question, mulitple .wars vs a single .war
I am in the early stage of architecting a web project.
At this point, I've came up with two solutions:
Multiple .wars
Each section would be it's own .war that would be built into an .ear. This would allow a multiple developers to work on the project and if a change would be made, then only the changed .war would need to be built.
However, then I would have mulitple copies of the same library for each .war, so that could slowly become a maintenance nightmare.
Also, I haven't figured out how to communicate between each .war - I don't believe I can cross container context?
Single .war
I wouldn't have to worry about multiple copies of the same library files. Nor would I have to worry about losing session data between applications since I would be running under one container.
But I am unsure of the best way to have more than one developer work on the project? It was suggested that I look at cruise-control at sourceforge.net - an automated build process - thus developers could check in their source code and a build would happen every xx minutes.
What is the best way to approach a project that is made up of multiple applications that need to be under one application suite?
Thanks,
--Todd
