Not to give an obnoxious answer, but the easiest way is to fix the condition that is causing the warning to be generated. I am in the middle of on upgrade to 0.9x and I am fixing near hundreds of these types of messages generated by our reports. Most of the time it is an easy fix to a padding property or a mis-set height, but sometimes it requires going through several layers and figuring out what is adding up to cause the warning. I feel these warnings are good indicators of things that may not be "just right" and should be looked at to make sure they are not causing any layout problems.
There is a basic wiki on this here: http://wiki.apache.org/xmlgraphics-fop/Troubleshooting/CommonLogMessages With that said, I believe you can just turn off warning messages in the logger, but then you might miss something you need. -Lou AlliumPorrum <[EMAIL PROTECTED]> wrote on 02/15/2008 05:28:16 AM: > > Sometimes FOP writes some warnings & infos to my app servers log, and often > they also contain some information about the actual content of the document, > for example: > > 11.2.2008 14:29:45 org.apache.fop.layoutmgr.PageBreakingAlgorithm > updateData2 > WARNING: Part/page 0 overflows the available area in block-progression > dimension. (fo:static-content, "xxxxxx") > > How could I get rid of these?? I mean, I don't want that FOP writes any > logging information that might contain any parts of the actual parsed > document? > -- > View this message in context: http://www.nabble.com/Getting-rid-of- > all-warning-messages-in-logs--tp15497827p15497827.html > Sent from the FOP - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
