You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2005/11/10 08:40:09 UTC

DO NOT REPLY [Bug 37427] - Redirect stdout and stderr to logging system

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37427>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37427





------- Additional Comments From skitching@apache.org  2005-11-10 08:40 -------
This functionality definitely does not exist in commons logging.

However commons-logging uses "adapters" to map to various logging libraries, and
has the ability for an application to override the adapter used via a number of
mechanisms (system property, commons-logging.properties file, service file)
which are documented. 

I think you could write a custom adapter which sets up this stdout/stderr
override stuff when loaded, and configure commons-logging to use it.

I wouldn't be particularly interested in seeing this feature in core
commons-logging though; commons-logging is mainly for use by libraries, and
libraries shouldn't be writing to stdout or stderr. Applications which need to
trap this should know what underlying logging lib is being used, and can
therefore set this stuff up themselves.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org