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.
[20040127] When you start the IDE, the described property value is null (at least the property sheet claims it). Fortunately this is not affecting the IDE's ability to stop catalina. The conf/server.xml contains the right value (default 8005). If you change the property value, the change is propagated into the server.xml correctly and the property value is displayed right.
Just a humble hint: This problem happens even if the IDE is non run for the first time with clear userdir. You encounter the some problem when the 'jakarta-tomcat-5.0.16_base' directory with valid conf/server.xml is in you userdir. So the problem is not caused by missing jakarta-tomcat-5.0.16_base/conf/server.xml when you run IDE for the first time.
Marek, you got it right. I saw this in code and was going to ask Martin (who implemented this) why he wants this to fail if the xml file cannot be reached. I guess he only tested this for manually added instances, bot the bundled one. I guess the ideal implementation would be to take/store the value in InstanceProperties if the xml cannot be reached and then apply the value in server xml when creating home and base dir for bundled tomcat. I guess this is not very likely to be encountered by he user (it is ok after you first start the server) and there is an easy workaround so IMO this is a P4.
I guess you mixed up this bug with #39331.
I'm not sure about the latest code, since we did this together with Milan, but i'll look at it.
Fixed in trunk: http://tomcatint.netbeans.org/source/browse/tomcatint/tomcat5/bundled/src/org/netbeans/modules/tomcat5/bundled/layer.xml.diff?r1=1.6&r2=1.7 http://tomcatint.netbeans.org/source/browse/tomcatint/tomcat5/src/org/netbeans/modules/tomcat5/nodes/TomcatInstanceNode.java.diff?r1=1.18&r2=1.19
verified