different WAR files, shared resources

Question

Suppose you have several applications which share the same code and most of the other resources, but have a somewhat different look and feel, some labels change, etc. (thin

Answer 1

Thanks for the replies so far, but I'm afraid I forgot to mention that the WARs will be deployed in different environments that are completely isolated from each other.

So maybe having a common WAR deployed next to the actual application is the only option. I think I'll go with the following:

• WAR1, WAR2 containing app-specific stuff
• CommonWAR containg common stuff (no kidding)
• EAR1: WAR1 + CommonWAR, to be deployed in env1
• EAR2: WAR2 + CommonWAR, to be deployed in env2