You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Nigel Sim (JIRA)" <ji...@apache.org> on 2012/07/09 12:10:34 UTC
[jira] [Updated] (MTOMCAT-167) Add the ability to specify
context.xml files for each additional Webapp being deployed
[ https://issues.apache.org/jira/browse/MTOMCAT-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nigel Sim updated MTOMCAT-167:
------------------------------
Attachment: contextFile-tomcat6.patch
This patch adds a field, contextFile, to the Webapp object, and uses this instead of the "global" contextFile if specified.
Also, I've put in a check for the contextPath so that it doesn't prepend a / if there is already one there. This makes contextPath and path both behave in the same way, which I think is what would be expected.
> Add the ability to specify context.xml files for each additional Webapp being deployed
> --------------------------------------------------------------------------------------
>
> Key: MTOMCAT-167
> URL: https://issues.apache.org/jira/browse/MTOMCAT-167
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
> Affects Versions: 2.0-beta-1
> Reporter: Nigel Sim
> Attachments: contextFile-tomcat6.patch
>
>
> Being able to deploy multiple webapps in an embedded container is fantastic, but currently they all inherit the same context file, which means that you can end up with namespace issues, and perhaps requiring context params (such as crosscontext) which you would rather not set on all the webapps.
> As there is now good support for multi-war configurations, it'd be good to extend this to support separate context files for each war.
> ie, I'd hope to do something like:
> <webapps>
> <webapp>
> <groupId>portals</groupId>
> <artifactId>portal-container</artifactId>
> <version>1.9</version>
> <contextPath>/container</contextPath>
> <contextFile>${basedir}/portal-container-context.xml</contextFile>
> </webapp>
> </webapps>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org