xmlgraphics-fop-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nancy_b <nancy_br...@yahoo.com>
Subject Re: Log4j Woes
Date Tue, 25 May 2010 14:11:52 GMT

How do I find FOP's classpath and place log4j jar there?

Thanks a lot in advance!!!
nancy
  

Peter Hancock-2 wrote:
> 
> Hi Nancy,
> 
> I have just realised that you are using fop via the package manager, and
> not
> from a direct fop download - whoops!
> I am sorry, but I am not sure I can help with your configuration.  Perhaps
> there is a Debian mailing list that might help?  I wonder if the
> LOG4J_OPTS
> variable is used by java-wrappers.sh script referenced in the fop script?
> Maybe you could email the author fourmond@debian.org?
> 
> If you have no luck you could alternatively checkout fop with subversion
> and
> run that using the configuration discussed in my last response.  This will
> require a bit more work to set things up, but it is well documented at
>  http://xmlgraphics.apache.org/fop/quickstartguide.html
> 
> I am for the confusion caused by my assumption about your fop setup!
> 
> Pete
> 
> On Tue, May 25, 2010 at 11:33 AM, nancy_b <nancy_brndt@yahoo.com> wrote:
> 
>>
>> Hi dear Peter,
>>
>> Thank you for your prompt response!!!
>> --First put the log4j jar in fop's lib directory
>>
>> I don't have such a directory. I do have
>> 1) /usr/bin/fop (where fop is the script)
>> 2) /usr/share/java/fop-0.95.jar and /usr/share/java/fop.jar
>>
>> --Put your log4j.xml file in the root of the fop project.
>> where is this exactly?
>>
>> -Uncomment the following line...
>>
>> I dont have such a line. Here what I have in the fop script:
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> #! /bin/sh
>> # Shell script wrapper around the fop program,
>> # Copyright 2008 by Vincent Fourmond <fourmond@debian.org>
>> #
>> # Licensed under the same terms as fop itself, that is under
>> # the conditions of the Apache 2 licence.
>>
>> # Include the wrappers utility script
>> . /usr/lib/java-wrappers/java-wrappers.sh
>>
>> # comment this line if you want fop to run without headless property,
>> # or write a line containing
>> #  HEADLESS=
>> # in your fop configuration file.
>> HEADLESS=-Djava.awt.headless=true
>>
>> # Load system-wide configuration, if any
>> if [ -f /etc/fop.conf ]; then
>>    . /etc/fop.conf
>> fi
>>
>> # Load user's preferences, if any
>> if [ -f "$HOME/.foprc" ]; then
>>    . $HOME/.foprc
>> fi
>>
>> # We prefer to use openjdk or Sun's java if available
>> find_java_runtime openjdk sun  || find_java_runtime
>>
>> find_jars commons-io avalon-framework serializer xalan2 xml-apis
>> find_jars batik-all commons-logging servlet-api xercesImpl
>> xmlgraphics-commons
>> find_jars xml-apis-ext
>>
>> # We load the hyphenation jar at the request of the user.
>> if [ "$FOP_HYPHENATION_PATH" ]; then
>>    find_jars $FOP_HYPHENATION_PATH
>> fi
>> find_jars fop
>>
>> run_java $HEADLESS org.apache.fop.cli.Main "$@"
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> Please advise!
>>
>> thanks a lot in advance!!!
>> Nancy
>>
>>
>> Peter Hancock-2 wrote:
>> >
>> > Hi Nancy,
>> >
>> > I am not sure how the LOG4J_OPTS environmental variable is supposed to
>> be
>> > handled by the log4j library (I would like to know!) so I would
>> recommend
>> > changing the fop script.
>> >
>> > First put the log4j jar in fop's lib directory.  You can download it
>> from
>> > http://logging.apache.org/log4j/1.2/manual.html
>> > Put your log4j.xml file in the root of the fop project.
>> > Edit fop:
>> > Uncomment the following line
>> > *
>> >
>> LOGCHOICE=-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger
>> > *
>> >
>> > edit the fop_exec_command variable (bottom of fop file) to include
>> >  -Dlog4j.configuration=log4j.xml
>> >
>> > This approach will keep the log4j config local to fop which is
>> preferred.
>> > Other java applications using log4j would want different config.  Also
>> you
>> > should not have to modify /usr/share/java since it is managed by
>> Debian.
>> >
>> > I hope this works for you
>> >
>> > Pete
>> >
>> > On Mon, May 24, 2010 at 9:01 PM, nancy_b <nancy_brndt@yahoo.com> wrote:
>> >
>> >>
>> >> Hi Pete,
>> >>
>> >> Thanks a lot for your prompt response!!!
>> >>
>> >> -- Did you change the fop script to specify the LOGCHOICE variable?
>> >>
>> >> No, why should I? I didn't do anything in my previous Linux, and it
>> was
>> >> fine...
>> >>
>> >> --Also, is the log4j.jar on your classpath too?
>> >>
>> >> Don't know, how do I check that??
>> >>
>> >> Please, advise! ;-)
>> >>
>> >> My best wishes,
>> >> Nancy
>> >>
>> >>
>> >>
>> >> Peter Hancock-2 wrote:
>> >> >
>> >> > Hi Nancy,
>> >> >
>> >> > Did you change the fop script to specify the LOGCHOICE variable?  At
>> >> the
>> >> > bottom of the fop script you will find some  commented out examples
>> of
>> >> > setting this variable.  The convention is to name the log4j file
>> >> > log4j.xml,
>> >> > but it should not matter as you refer to it explicitly with the
>> >> LOG4J_OPTS
>> >> > system variable.  Also, is the log4j.jar on your classpath too?
>> >> >
>> >> > I hope this helps,
>> >> >
>> >> > Pete
>> >> >
>> >> >
>> >> > On Mon, May 24, 2010 at 4:25 PM, nancy_b <nancy_brndt@yahoo.com>
>> wrote:
>> >> >
>> >> >>
>> >> >> Hi Folks!
>> >> >>
>> >> >> I use FOP 0.95 to compile PDF documents from DocBook sources on
my
>> >> Linux
>> >> >> Debian machine. After upgrading my Debian to v5.2, I get the
>> following
>> >> >> log4j-related problem:
>> >> >>
>> >> >> fop -c /home/cozy/doc/xsl/myconf.xml -fo  \
>> >> >>          user_manual.fo -pdf  user_manual.pdf
>> >> >> log4j:WARN No appenders could be found for logger
>> >> >> (org.apache.fop.util.ContentHandlerFactoryRegistry).
>> >> >> log4j:WARN Please initialize the log4j system properly.
>> >> >>
>> >> >> and FOP does not produce any compilation-related warnings that
I
>> >> expect
>> >> >> it
>> >> >> to print in the console.
>> >> >> 2.6.18.3
>> >> >> I did not have this problem before (on my Debian v.2.6.18.3).
>> >> >>
>> >> >> After reading related posts on this forum, I did the following:
>> >> >>
>> >> >> 1) Created a log4j conf file (log4j-properties.xml) with the
>> following
>> >> >> contents:
>> >> >>
>> >> >> <?xml version="1.0" encoding="UTF-8" ?>
>> >> >> <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
>> >> >>
>> >> >> <log4j:configuration
>> xmlns:log4j="http://jakarta.apache.org/log4j/">
>> >> >>  <appender name="console" class="org.apache.log4j.ConsoleAppender">
>> >> >>
>> >> >>    <layout class="org.apache.log4j.PatternLayout">
>> >> >>
>> >> >>    </layout>
>> >> >>  </appender>
>> >> >>  <appender name="logfile" class="org.apache.log4j.FileAppender">
>> >> >>    <layout class="org.apache.log4j.PatternLayout">
>> >> >>
>> >> >>    </layout>
>> >> >>  </appender>
>> >> >>  <!-- ALL | DEBUG | INFO | WARN | ERROR | FATAL | OFF
>> >> >>  <root>
>> >> >>    <priority value ="warn" />
>> >> >>    <appender-ref ref="console" />
>> >> >>    <appender-ref ref="logfile" />
>> >> >>  </root>-->
>> >> >>  <logger name="org.apache.fop">
>> >> >>    <level value="warn"/>
>> >> >>    <appender-ref ref="console" />
>> >> >>  </logger>
>> >> >>  <logger name="org.apache.xmlgraphics">
>> >> >>   <level value="warn"/>
>> >> >>   <appender-ref ref="console" />
>> >> >>  </logger>
>> >> >> </log4j:configuration>
>> >> >>
>> >> >> It sits together with log4j in the /usr/share/java/ directory.
I
>> also
>> >> >> placed
>> >> >> there the log4j.dtd file.
>> >> >>
>> >> >> 2) In bashrc, I defined the following:
>> >> >>
>> >> >> export
>> >> >>
>> >>
>> LOG4J_OPTS="-Dlog4j.configuration=/usr/share/java/log4j-properties.xml".
>> >> >>
>> >> >> But, guess what? It did not help at all. I still get the log4j
>> >> message.
>> >> >> The
>> >> >> posts also mention that it is necessary to define the conf. file
in
>> >> the
>> >> >> classpath. I have no idea what it is and how to find it....
>> >> >>
>> >> >> Please, people, help! :-(
>> >> >>
>> >> >> Thanks a lot in advance!!!!
>> >> >> nancy
>> >> >>
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >> http://old.nabble.com/Log4j-Woes-tp28658124p28658124.html
>> >> >> Sent from the FOP - Users mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >>
>> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail:
>> fop-users-unsubscribe@xmlgraphics.apache.org
>> >> >> For additional commands, e-mail:
>> fop-users-help@xmlgraphics.apache.org
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >> http://old.nabble.com/Log4j-Woes-tp28658124p28661171.html
>> >> Sent from the FOP - Users mailing list archive at Nabble.com.
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
>> >> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Log4j-Woes-tp28658124p28666753.html
>> Sent from the FOP - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
>> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>>
>>
> 
> 

-- 
View this message in context: http://old.nabble.com/Log4j-Woes-tp28658124p28668895.html
Sent from the FOP - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org


Mime
View raw message