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.
[010517] You have to iWS plugin installed. If you start IDE for the first time, Tomcat is default server. If you restart IDE then iWS server is as default. This happens only if you didn't look at or set default server. How to reproduce: 1. Unzip new build, clean user directory and install iWS plugin. 2. Run IDE. Now Tomcat is as default server, but don't look at Installed Servers settings. You must trust me that tomcat is default. Don't do anything, just exit IDE. 3. Start IDE. Now look at Installed Servers settings. Now iWS is default server.
If a tree falls in the forest and nobody is there to see it, does it make any sound? In other words, why is this a bug if there are no observable user issues?
I see observable user issue: User will install IDE and will execute some JSP. It will be executed on Tomcat. But if user execute JSP after restart, JSP will be suddenly executed on iPlanet although user didn't change anything.
How are you exiting the IDE? If you're not using File->Exit then the Project Settings won't get written to disk, so the default server is not saved. Please confirm that this is the situation.
I exited IDE correctly. Tomcat is default server with first start of IDE. If I look at Server Registry node or execute some JSP then Tomcat remains as default server after restart. But if I don't execute JSP or don't look at Server Registry node then iWS become default server after restart.
This bug causes other problem. If some breakpoints are added to JSP and IDE is restarted then error appears during startup: Errors occured while opening project: org.netbeans.modules.debugger.support.DebuggerProjectSettings See bugtraq bug #4460508
I played with this bug and I couldn't find when exactly default server is changed, but it's changed very often (almost vith every restart) and even if default server was previously manually set. Also I found other serious issue. If DebuggerProjectSettings error appears during startup then default server can't be changed. No message, no exception, but old default server still remains.
As to the relation to the debugger bug - this bug isn't related to the debugger bug - the debugger bug is because the order of deserializing system options causes problmes (see explanation below). This bug originally was that the default server was undefined before the default server was accessed, which is P3. The Debugger SystemOption reestablishes breakpoints. The j2eeserver SystemOption sets the default webserver. These SystemOptions are unrelated, and in practice the debugger option gets deserialized first. However, when the breakpoint is in a jsp, and the debugger tries to reestablish breakpoints in the jsp, the JspDataObject looks up the default webserver, which hasn't been deserialized yet, and so an exception is thrown. This has the feel of a problem that could be solved by lazy initialization either in JspDataObject or in the Debugger settings.
Changing to P3 as per last comment.
fixed. New settings loading will fix the problem