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 119504 - [60cat] Keep server output window visible after deployment
Summary: [60cat] Keep server output window visible after deployment
Status: NEW
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-19 17:58 UTC by goeh
Modified: 2009-12-10 12:56 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description goeh 2007-10-19 17:58:12 UTC 
When deploying to glassfish NetBeans Output window first switches to the ant output (run-deploy), then to the 
glassfish output, and finally switches back to the ant output window. I guess the logic is to follow output, and the 
ant window is the last one writing output.
But... I always want to see the glassfish output window immediately after deploying. Right now I'm using the mouse to 
activate the glassfish window. But I do that 100 times per day and find it annoying.
Maybe a service property would be nice that allowed me to "keep output window visible after deployment". Or make it 
default to keep the server window visible if there was no error during deployment.

Aaron Hagopian writes:
I too have been annoyed by this but with tomcat.  I only want to see the ant output if there was an error otherwise I 
want the server output as well.
Comment 1 Jesse Glick 2007-10-19 18:38:06 UTC 
No plans to make any special-case behavior for processes that happen to run Glassfish. However note that the Ant output
window will not forcibly appear at all unless (1) some warning/error appears, (2) input is potentially requested. If the
task which starts Glassfish forks an external process and does not explicitly disable input then #2 will hold. (There is
no way for the Ant module to know that no input is actually being asked for from an external process, due to the nature
of stdio streams across OS processes.) If neither #1 nor #2 happen, then no focus should be requested by the Ant module.
Comment 2 Vince Kraemer 2007-12-19 06:09:40 UTC 
this looks fixable.
Comment 3 Vince Kraemer 2008-01-31 18:40:18 UTC 
It sounds like this may require a bit more thought...

based on what Jesse said...

here is the sequence:

ant starts
ant output opens
see lines from ant
server needs to start
server starts
see lines from server

If there is a server error
  error info goes into server log
  error message gets sent to ant 
  ANT DISPLAYS ERROR -- so it gets the focus

If there isn't a server error
  normal info goes to server log
  ant prints more messages (but may not get the focus)
  in this case there isn't an interesting message in the server log... but it may end up being the "front" window...
Comment 4 Vince Kraemer 2009-12-10 12:56:45 UTC 
no issue should be assigned to issues. redistributing the load