Please use the Apache issue tracking system for new NetBeans issues (https://issues.apache.org/jira/projects/NETBEANS0/issues) !!
Bug 90508 - Add logging level based message filtering
Add logging level based message filtering
Status: RESOLVED WONTFIX
Product: platform
Classification: Unclassified
Component: Output Window
6.x
All All
: P2 (vote)
: TBD
Assigned To: Milos Kleint
issues@platform
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-12-04 10:35 UTC by Sherold Dev
Modified: 2008-12-22 21:51 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sherold Dev 2006-12-04 10:35:10 UTC
It would be useful to be able to filter out selected logging levels

FINE, INFO, WARNING, ERROR, etc.
Comment 1 Milos Kleint 2006-12-04 12:26:47 UTC
please specify what the usecase is. Debugging? 
Any specific messages you consider useful?
Comment 2 Sherold Dev 2006-12-04 13:16:21 UTC
For example if you develop a web application targeted to Tomcat, the server
output is full of info message which you usually do not care about. 

e.g.:

Dec 4, 2006 2:07:15 PM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8084
Dec 4, 2006 2:07:15 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 695 ms
Dec 4, 2006 2:07:15 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Dec 4, 2006 2:07:15 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.17
Dec 4, 2006 2:07:15 PM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Dec 4, 2006 2:07:16 PM org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8084
Dec 4, 2006 2:07:17 PM org.apache.jk.common.ChannelSocket init
INFO: Port busy 8009 java.net.BindException: Address already in use
Dec 4, 2006 2:07:17 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8010
Dec 4, 2006 2:07:17 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=1 time=0/29  config=null
Dec 4, 2006 2:07:17 PM org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
Dec 4, 2006 2:07:17 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 1785 ms
Dec 4, 2006 2:07:27 PM org.apache.catalina.startup.HostConfig checkResources
INFO: Undeploying context [/WebApplication12]

What you are interested in are only the WARNING and ERROR message, however, in
case of some error you might want to take a look also at the INFO messages and
thus not logging the INFO message at all is not an option.

The same example might apply also in the J2SE development.
Comment 3 Antonin Nebuzelsky 2006-12-14 15:45:24 UTC
This is not realistic to do in a general way in Output Window code.

You should do it in your code as the provider of the stream for Output. Adding
buttons to Output window is possible via APIs. You can do the filtering of the
stream in your code and reload it to the Output Window.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo