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 52298 - HTTP and Output Window Tabs are not controllable
Summary: HTTP and Output Window Tabs are not controllable
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Sherold Dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-10 17:28 UTC by ssoong
Modified: 2005-02-17 15:55 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ssoong 2004-12-10 17:28:21 UTC
netbeans-4_1-daily-bin-200412051900-windows-
5_Dec_2004_1900.
JDK 1.5 building for JDK 1.4.

These problems have been occuring since version 
4.0 .
When you run a JSP /context/a.jsp from NB,
the Output window would spontaneously appear (as 
well as the HTTP Monitor Window). The Output 
window would normally be comprised by
- Tomcat output tab context
- Compile tab for context
- context log tab

On each of these tabs, there is an x to close 
them individually.

These are the compounded problems I face:

1.
So I accidentally closed Tomcat output tab.
There is no way in the menu I could bring back 
that tab. Tomcat output tab is where all the 
System.out goes. Now I cannot see my println 
debug lines.

This, I propose, is a bug, but I suggest the 
following to treat it.
Suggestion 1:
It would be nice to have the menu->Window-
>Output to further break out into another drop 
down to let us choose which tab to activate.
Suggestion 2:
Alternatively, right click on Output window 
allows me to activate the appearance of tabs.

2. I cleared the context log of all the 
exception errors (and other what-nots). I 
closeed the Output window. Then exited NB. 
Restarted NB, ran the JSP. The Output window 
appeared spontaneously (without my preciously 
desired Tomcat output tab) - and the context log 
tab is filled with error messages of eons ago 
which I had supposedly cleared. I did not 
experience this in version 4.0.

3. OK, this item should have been in another 
issue#. Anyway.... I close the HTTP Monitor. It 
keeps on reappearing spontaneously everytime a 
JSP is run. No, no, no - I don't want to see 
that window. Don't compel me to see that window. 
My mind is too cluttered to really care what's 
happening at the HTTP stream yet. No, I don't 
even want it hiding at the bottom, because my 
mind is too cluttered I simply need to see one 
thing there - the output window. Can someone 
just let me let a means to crucify that HTTP 
window and let it Rest In Peace, until I 
consciously choose to resurrect it?

4. Hmmm... how about, starting/stopping Tomcat 
from Tomcat output tab? Alright, I'll put this 
as a suggestion in another issue when I have the 
time.

.... Help, help, help - & thank you.
(Despite these reflection of annoyance, I am 
thoroughly appreciative about increasingly 
better stuffs you people are providing that I 
have not used my JBuilder for quite some time - 
so happy holidays!:~)
Comment 1 Petr Pisl 2005-02-17 15:05:59 UTC
Stepan, it's all about the opening output window. Can you look at
this. If this is a problem in output window itself, please reasign to
the core.
Comment 2 Sherold Dev 2005-02-17 15:55:52 UTC
Marking as invalide since this is a bunch of different issues, some of
those are duplicates or invalide.

Please report each issue separately next time, thanks.

1.

you can reopen the Tomcat's output from the runtime tab -> server
registry -> tomcat instance context menu -> "view server output" action

2. 

This issue 50497 is already filed.

3.

There is an issue 49592 file for this.

you can disable the http monitor: go to the runtime tab -> server
registry -> tomcat instance context menu -> properties -> enable http
monitor.

4. 

There are plans to move servers from the runtime tab, this will be
done probably in 4.2.