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.
[nb36-rc1, solaris9x86] I encountered the problem in a particullar situation which IMO can happen to users -easily-. I had installed a tomcat5 server on the solaris machine, but the $CATALINA_HOME/bin/catalina.sh script had no execution right. Then added this installation into IDE server registry and tried to execute it. The Server Status Window appeared and shown an error message that the script could be executed. So far so good. Unfortunately the message remained at most for a second and the was replaced by message "Waiting for Tomcat". I am aware that this case is rather an user error, but I am not sure that this situation (replaced error message) can happen also in other situations. This would be really bad. Moreover the message "Waiting for Tomcat" seems to remain forever until you close the dialog or try to start it again. I would also like to have Ann's opinion on this (mostly UI?) issue.
I think that any user level error messages (i.e. definitely anything we show in progress dialog) should be written to output window. Not sure how this would coexist with the output from tomcat process though. Perhaps a high level status should be written to the standard output tab by j2eeserver and then individual plugins can use a separate tab for details like tomcat is now doing. On a similar topic: We discussed the server progress dialog with Ann and we agreed that for deployment there should definitely be more info written into output tab. Something like: "copying files.., restarting/redeploying the web module.., etc.". When we switch to running the deployment tasks from ant this will become very natural as ant tasks often write info about what they are doing. Any errors need to be reported there in the first place. I though that this could all be tracked under this issue (since you have chosen such a good description in Summary field!).
Maya is working on UI spec for improving j2eeserver. This should be consisdered. Printing out messages could be done for promoD if time permits.
Still planning to remove the progress dialog, but did not make it into 4.1. With ant based deployment all messages will be in output tab...
I consider this to be fixed - the messages are written to the output so you can read it even after closing the dialog.
Verified