On 17 April 2015 09:37:40 BST, Dominic Hargreaves <d...@earth.li> wrote:
>On Wed, Apr 15, 2015 at 08:33:00AM -0500, Mark Thomas wrote:
>> On 15/04/2015 05:28, Dominic Hargreaves wrote:
>
>> > I am running the Tomcat manager application via a Debian package
>> > (tomcat8-admin), which deploys the webapp from
>> > /usr/share/tomcat8-admin/manager. We ran into a problem hitting th 
>> > maximum upload size (configured as the multipart-config element in
>the
>> > HTMLManager servlet block). This is easy to fix if you're willing
>to
>> > edit Debian-packaged files, but this is incorrect: files in
>/usr/share
>> > are owned exclusively by dpkg. Is there a way to override this
>element
>> > from somewhere in tomcat's conf directory (which is symlinked to
>> > /etc/tomcat8 in Debian)?
>> 
>> No. The web application setting would take priority.
>
>Okay, thanks for confirming.
>
>> > If it's not possible to override this at the moment, then is this a
>bug
>> > in Tomcat, or the Debian packaging?
>> 
>> I'd say the bug is in the Debian packaging (but I would say that
>> wouldn't I).
>> 
>> Without know how Tomcat is packaged in Debian, I would expect the
>following:
>> - the Manager web application to be a separate, optional package
>
>Yep, it is.
>
>> - the web.xml to be placed in an appropriate location for users to be
>> able to edit it.
>> 
>> I took a quick look through the web.xml for the Manager app. There
>are
>> plenty of settings I wouldn't expect to change but there are a
>handful
>> of things that users might want to tweak.
>> 
>> In theory, it should be possible to move those settings to
>context.xml
>> but that would require code changes and would mean do things that
>were
>> contrary to the spirit of the servlet spec so there would likely be
>> resistance to such changes from the Tomcat community.
>> 
>> One option would be for Debian to use external entities for the
>> configurable elements and place the file that defines those entities
>> somewhere where users can edit it.
>
>Okay, that's an interesting idea if it's possible to agree on a sane
>set :)
>
>Thanks for your feedback!

Another option (I think) is to use the property replacement feature. I.e. 
${property.name} in web.xml and property.name=foo in catalina.properties

The only question is if this works in web.xml which I don't recall and I don't 
have easy access to the source to check. If it doesn't work we should be able 
to fix that easily. 


Mark


>
>Cheers,
>Dominic.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>For additional commands, e-mail: users-h...@tomcat.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to