Ok, however I still cannot find a solution for eliminating fop debugging and I tried all the suggested solutions. I even added the log4j.logger.org.apache.fop = FATAL in the log4j.properties in the oc4j directory but no luck. Any clue?
Jeremias Maerki-2 wrote: > > A direct connection between logging and FOP isn't necessary anymore like > it was with FOP 0.20.5. We simply use Commons Logging and leave the > configuration of the user's preferred logging subsystem to the user. > > More info here: > http://wiki.apache.org/xmlgraphics-fop/HowTo/SetupJDK14Logging > http://jakarta.apache.org/commons/logging/commons-logging-1.0.4/docs/guide.html > > On 16.07.2007 10:42:05 juanita wrote: >> >> Ok I set the jar correctly in the classpath and now in the class where I >> initiate the fop and >> specifically the fopFactory I am doing the following: >> >> logFactory = LogFactory.getFactory(); >> logFactory.setAttribute("level", "fatal"); >> >> however again I see all the fop messages. >> Shouldn't I connect fop with logFactory in a way and if yes how can I do >> that? >> > > <snip/> > > > Jeremias Maerki > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Package-messaging-is-missing-from-fop-0.93-tf4028223.html#a11670310 Sent from the FOP - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
