[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3119) Multiple WAR in EAR verification, example, and document

[ https://jira.jboss.org/jira/browse/JBSEAM-3119?page=com.atlassian.jira.pl... ] Stuart Douglas commented on JBSEAM-3119: ---------------------------------------- I considered using the context path but rejected it for a few reasons. The main one is to do with the concept of a default application to maintain compatibility with the existing API's. If you use the context path as the application name you would need to use a context param to specify the default application. The reason why I think that the default application concept is nessesary is so that people who have been developing a single war project and use the lifecycle API or spring integration do not have to change any code when going to a multi-war application. The other reason why is because I don't realling like overloading the meaning of the context path with no good reason, it only takes a minute to add another context param. If nothing else it is more likely to make them read the (hopefully soon to exist) section of the docs that explains seams behvaiour in a multi war applicaiton. With that said I don't think it makes that much difference either way, it is not a hard change so just go with the majority I guess. There is not much point arguing about it until we know that this patch is actually going to make it in. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira