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.
Bug exists in FCS RC4 FFJ build on Linux RH 7.2 and Windows 2000. In the very first session of FFJ (after installation) the default Web Tier Applications server is set to "No Default" instead of embedded TC instance. It may have very negative impact on the users who're using FFJ for the first time. How to reproduce: 1. Install RC4 build from installer 2. Start ide (runide -userdir <dir>) 3. Switch to Runtime tab in Explorer and notice that Server Registry->Default Servers->Web Tier Apllications is set to No default (see attached picture).
Created attachment 5890 [details] snapshot of Explorer window
looks like problem in the server registry
I tried to reproduce: rc5.exe; win2000; jdk 1.4 - no bug rc4.bin; rh 6.2; jdk 1.4 - no bug
We are currently unable to reproduce this bug. It seems like it was either a fluke occurrence or it is some intermittent timing issue. I am marking the bug as "WORKSFORME" and assigning to QA to do further investigation after the FCS test cycle.
Seems that the reason of the bug is caused by the intermodule problems between app server plugins (RI and WL plugins) and web server plugin (TC plugin). Thus when app server plugin is loaded prior TC plugin and sets the default app server to one of its instnces, then TC is not able to set its instance as default web server. There are 2 ways to reproduce it: 1. Without IDE restarting: a. Disable all J2EE app server plugins (RI and WL) b. Disable/enable TC plugin and notice that default web server is set correctly c. Enable app server plugin - default app server should be set correctly d. Disable/enable TC plugin and notice that default web server is NOT SET properly 2. With IDE restarting (to force the plugins being loaded in the correct order): a. Move TC plugin .jar file to some temp location b. Start IDE and verify that default app server is set ploperly c. Exit from IDE and move TC plugin .jar file back to modules dir d. Start the IDE and notice that TC doesn't set its instance as default web server !
Set target milestone to TBD
target 4.0
This issue is still relevant in the NetBeans 3.6 code base. This is a highly visible usability issue; raising priority to P2. Since Nam is already working on this issue, I am reassigning this to Nam.
An additional requirement is that it should be possible to control the default server from the outside of the j2eeserver module, especially from the installer.
cleaning up -- Nam fixed the issue with no default server, I filed the last comment from Petr as a separate issue (http://www.netbeans.org/issues/show_bug.cgi?id=37953) and I'm closing this one.