I have to admit I'm in a bit of a quandary. I need to clone a seam application and place it under new virtual domain name. The business logic should remain the same, while the presentation layer and the DB will change.
The easiest option would be to build an EAR for each of the hosts, where only WAR and persistence.xml would be different. One of the drawbacks of this solution is that there is a copy of the JAR in all EARs, and if I need to make a change in actions, I would have to rebuild all EARs.
Before writing this message I thought I'd much like to see a single instance of JAR, but that would require a single of EAR as well, and that in turn would require reloading the whole set of webapps to make a single change in any of the webapps. Please, correct me if I'm wrong here.
Right now I'm thinking that creating multiple EARs for each of the virtual hosts isn't a bad solution, given that the process bulding those EARs is automated with ant.
Has anyone had to solve this kind of task of cloning and putting clones under the different domain names?
I would think from a QA perspective building separate copies of apps makes the most sense. Also, you might not want to upgrade all apps at the same time.