incubator-odf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devin Han (Commented) (JIRA)" <>
Subject [jira] [Commented] (ODFTOOLKIT-289) Clean up unnecessary log messages
Date Tue, 11 Oct 2011 05:52:29 GMT


Devin Han commented on ODFTOOLKIT-289:

Clean up log messages which may confuse user in ODFDOM and Simple API.
Replace e.printStackTrace() with java.util.logging.Logger in SImple API.

> Clean up unnecessary log messages
> ---------------------------------
>                 Key: ODFTOOLKIT-289
>                 URL:
>             Project: ODF Toolkit
>          Issue Type: Task
>          Components: odfdom, simple api
>            Reporter: Devin Han
>            Assignee: Devin Han
> 22-Sep-2011 11:48:35 getTextPropertiesForRead
> INFO: No explicit text properties definition is found! 
> It is generated by the method getTextPropertiesForRead() in
> Logger.getLogger(CellStyleHandler.class.getName()).log(Level.INFO, "No explicit text
properties definition is found!", "");
> When cell has no text style setting, this log will be printed (maybe we should change
its level to "DEBUG").  It's just a tip or warning.
> We should probably try to eliminate any unnecessary log messages.  If there are no real
errors then by default we should not be writing to stderr or stdout;.  Why?  Think of the
multithreaded server scenario.  It is annoying for the server admin to have this written to
the log files, filling up their logs and making it harder for them to find important information.
 And on some servers, where stderr is unbufffered, this can be a performance problem.  You
have multiple threads all trying to write to stderr, and blocking for access.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message