[ https://issues.apache.org/jira/browse/ODFTOOLKIT-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15445068#comment-15445068 ]
Adrian commented on ODFTOOLKIT-289: ----------------------------------- The message is thrown once per cell, and it's pretty annoying find it filling up application logs. I totally agree it should be a debug message. Any workarround to avoid it? > Clean up unnecessary log messages > --------------------------------- > > Key: ODFTOOLKIT-289 > URL: https://issues.apache.org/jira/browse/ODFTOOLKIT-289 > Project: ODF Toolkit > Issue Type: Task > Components: odfdom, simple api > Reporter: Devin Han > Assignee: Devin Han > > 22-Sep-2011 11:48:35 org.odftoolkit.simple.style.DefaultStyleHandler > getTextPropertiesForRead > INFO: No explicit text properties definition is found! > It is generated by the method getTextPropertiesForRead() in > org.odftoolkit.simple.style.DefaultStyleHandler. > 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 was sent by Atlassian JIRA (v6.3.4#6332)