You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2014/09/09 18:32:07 UTC
[Bug 56937] New: Allow default context to be used when
deployXML=false and context.xml is in WAR
https://issues.apache.org/bugzilla/show_bug.cgi?id=56937
Bug ID: 56937
Summary: Allow default context to be used when deployXML=false
and context.xml is in WAR
Product: Tomcat 7
Version: 7.0.50
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: owen.farrell@gmail.com
With the changes in r1545288, any application that comes packaged with a
context.xml deployment descriptor requires a context-specific deployment
descriptor be present. While I understand the desire to improve security, it
still seems practical to inherit the default context.
Most IDEs that integrate with Tomcat will automatically generate an empty
context.xml. Some applications (like Artifactory) come with a minimalist
version.
Is there any way to account for both scenarios? Maybe adding a new host
attribute that allows the default context to be used. Or maybe the HostConfig
implementation could be improved so that only security-specific elements are
accounted for.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 56937] Allow default context to be used when deployXML=false
and context.xml is in WAR
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56937
Owen Farrell <ow...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |markt@apache.org
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 56937] Allow default context to be used when deployXML=false
and context.xml is in WAR
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56937
--- Comment #2 from Owen Farrell <ow...@gmail.com> ---
Mark - Sorry for the spam. I copied you on as the original implementer of the
change.
Konstantin - as for setting deployXml to true.... what if I don't want the
app-provided deployment descriptor? What if I want to use my default
context.xml? It seems like you've taken the management portion of container
management out of the hands of the container.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 56937] Allow default context to be used when deployXML=false
and context.xml is in WAR
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56937
Konstantin Kolinko <kn...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC|markt@apache.org |
Resolution|--- |WONTFIX
--- Comment #1 from Konstantin Kolinko <kn...@gmail.com> ---
Subscribing another person to automatic e-mail notifications without that
person's explicit consent affects your karma quite negatively.
You can always explicitly configure <Host deployXml="true"> so that
app-provided deployment descriptors were honored.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org