<?xml version="1.0" encoding="iso-8859-1" ?>

<document>

  <body>

    <faqs title="Logback Frequently Asked Questions">
      <part id="Logback Classic">
        <title>Logback Classic</title>
        
        <faq id="setup_jetty">
          
          <question>
						How can I use logback-classic with Jetty ?
					</question>

					<answer>
            <p>
              A few jars must be present in the
							<em>JETTY_HOME/lib</em>
							directory.
						</p>

            <p>
							Logback-classic is based on the SLF4J api. Therefore,
							the <em>slf4j-api-VERSION.jar</em> jar must be
							present. This jar can be downloaded from the <a
							href="http://www.slf4j.org/">SLF4J</a> project.
						</p>
						<p>
							Logback's own jars must also be present, namely 
							<em>logback-core-VERSION.jar</em> and
							<em>logback-classic-VERSION.jar</em> .
						</p>


            <!-- should logback.xml really be placed in JETTY_HOME?  -->

						<p>
							To configure logback-classic, a file called
							<em>logback.xml</em> should be placed at the root
							directory of Jetty, that is the <em>JETTY_HOME</em>
							directory. You can find configuration samples in the
							<em>examples/src/chapter4/conf/</em> directory, in the
							distribution of logback.
						</p>
					</answer>
				</faq>
				
				<faq id="auto_config">
          
          <question>
						How does the automatic configuration work?
					</question>

					<answer>
						<p>
							If a file called <em>logback.xml</em> is found in the
							classpath, then it is used.
						</p>
						<p>In case it is not found, a <em>logback-test.xml</em> file 
						is searched, and used if available.
						</p>
						<p>
							If none of these files are available, logback uses its 
							<code>BasicConfiguratory</code> class to create a simple default 
							configuration that will only log to the console.
						</p>
					</answer>
				</faq>
				
				
			</part>
		</faqs>
	</body>
</document>
