You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org> on 2012/03/01 19:27:57 UTC
[jira] [Updated] (BIGTOP-417) webapps shipped by bigtop components
should be using a system-provided Tomcat
[ https://issues.apache.org/jira/browse/BIGTOP-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated BIGTOP-417:
------------------------------------
Attachment: BIGTOP-417.patch.txt
Attaching the first rough cut of the packaging. Once this is approved I'll try to make Oozie and HTTPFS use this package instead of bundling the Tomcat.
> webapps shipped by bigtop components should be using a system-provided Tomcat
> -----------------------------------------------------------------------------
>
> Key: BIGTOP-417
> URL: https://issues.apache.org/jira/browse/BIGTOP-417
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.2.0, 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.3.0, 0.4.0
>
> Attachments: BIGTOP-417.patch.txt
>
>
> We now have at least 2 different components that squirrel away private copies of Tomcat (Oozie and HTTPFS). The right approach is to setup different instances of the system Tomcat via CATALINA_BASE (still pointing at a common, system-wide CATALINA_HOME). More on how it works here:
> http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
> http://willcode4beer.com/ware.jsp?set=tomcat_config
--
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