This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I think that 'edit server.xml' isn't enough, as I very often need to edit ${catalina.base}/conf/web.xml and ${catalina.home}/conf/web.xml, and look into ${catalina.base}/shared/lib and ${catalina.home}/shared/lib. I think a hierarchical menu like one presented below will make simple things like adding a framework to Tomcat or configuring default web-app options really simple. Local-> Edit 'server.xml' Edit 'web.xml' Folders-> / /shared/ /common/ Global-> Edit 'server.xml' Edit 'web.xml' Folders-> / /shared/ /common/ Or smth. else. Dunno, but I think this way will be better
Do you have any use cases, why is it necessary to edit Tomcat's web.xml files very often? Thanks.
Of course not often, but this possibility will not make UI worse. I.e. I want to make some frameworks and libs (Spring, JSTL, etc.) available by default I need then to change catalina.properties (add home paths to ${shared.loader} if I want make these frameworks available globally on Tomcat installation) and put .jar's in ${catalina.home}/shared/lib . While trying many choices of installation, I'ld need access these dirs very often.