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.
FFJ build 020501: 1) Open Explorer's 'Runtime' pane, expand Server Registry- >Default Servers. 'Web Tier Applications' should be set to 'Tomcat4.0 Internal....' 2) Now select Tools->Options, expand IDE Configuration- >System->Modules->Web->Tomcat 4.0 Server 3) Change 'Enabled' field to 'False' and click 'Ok' in the dialog which will be shown. 'Web Tier Applications' will be changed to 'No Defaults' 4) Now change 'Enabled' field to 'True'. 'Web Tier Applications' will be 'No Defaults' anyway. 5) Now choose 'Filesystems' pane in the Explorer window and after switch back to 'Runtime'. 'Web Tier Applications' will be set to 'Tomcat ...'. In my opinion it should be changed at once we have enabled the module.
Maybe bad refresh in J2EERegistry nodes. Milan can you evaluate this?
I cannot reproduce this on last builds(Netbeans 3.4). The behaviour seems to be correct : Web Tier Applications node is switching from "Tomcat4.0 Internal" to "No Defaults" and back according to the tomcat4.0 module status (enabled/disabled).
I'm still able to reproduce the bad refresh in NetBeans dev build 200301310100. If the Explorer is on the Runtime tab at the time that you re-enable the Tomcat 4.0 Server module, the Web Tier Applications node will still display "No Default". It will not refresh until you switch to another tab in the Explorer (for example, Filesystems) and then switch back to Runtime. If the Runtime tab is visible at the time the module is enabled, it should update immediately.
The issue was fixed by changing Server registry UI.