[
https://issues.apache.org/jira/browse/BIGTOP-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678223#comment-13678223
]
Robert Kanter commented on BIGTOP-939:
--------------------------------------
Yes, I also don't think everything can be done in catalina.properties; in fact,
looking at Oozie's catalina.properties, I don't think we've changed anything
from the defaults in there.
[~mackrorysd]'s approach sounds reasonable to me: start with a default/template
tomcat and then apply tweaks on top of it depending on the configuration
needed. For example, the only difference between the SSL Oozie and regular
Oozie is two XML files with only minor changes in them; instead of duplicating
the entire tomcat, it would be better to replace the two files at startup (this
is also similar to how Oozie switches between SSL and regular).
> Make usage of bigtop-tomcat more dynamic
> ----------------------------------------
>
> Key: BIGTOP-939
> URL: https://issues.apache.org/jira/browse/BIGTOP-939
> Project: Bigtop
> Issue Type: Task
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Priority: Blocker
> Fix For: 0.7.0
>
>
> Projects like Oozie and Sqoop present some configuration challenges compared
> to other components because they use Tomcat. Sometimes small tweaks to the
> configuration or classpath have to be done in a very component-specific way
> as opposed to tweaking files in /etc/<comp>/conf or /etc/default. In one
> case, we even have redundant Tomcat deployments for common configurations
> (Oozie's SSL vs. non-SSL).
> If the environment for Tomcat was generated more dynamically, we could avoid
> this redundancy and could allow common features to be configured in more
> "standard" ways.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
