[logback-dev] svn commit: r1136 - logback/trunk/logback-site/src/site/xdocTemplates

noreply.seb at qos.ch noreply.seb at qos.ch
Wed Dec 20 14:09:26 CET 2006


Author: seb
Date: Wed Dec 20 14:09:26 2006
New Revision: 1136

Modified:
   logback/trunk/logback-site/src/site/xdocTemplates/access.xml

Log:
removed duplicate information about PatternLayout

Modified: logback/trunk/logback-site/src/site/xdocTemplates/access.xml
==============================================================================
--- logback/trunk/logback-site/src/site/xdocTemplates/access.xml	(original)
+++ logback/trunk/logback-site/src/site/xdocTemplates/access.xml	Wed Dec 20 14:09:26 2006
@@ -280,176 +280,14 @@
 			flexible as the <code>PatternLayout</code> found in logback
 			classic.
 		</p>
-
-    <p>
-		  Logback access <code>PatternLayout</code> offers the following
-		  possibilities:
-		</p>
-		<table border="1" CELLPADDING="8">
-			<th align="center">Conversion Character or Word</th>
-			<th align="center">Effect</th>
-
-		<tr>
-			<td align="center"><b>a / remoteIP</b></td>
-			<td>
-				<p>
-					Remote IP address.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td align="center"><b>A / localIP</b></td>
-			<td>
-				<p>
-					Local IP address.
-				</p>
-			</td>
-		</tr>		
-		<tr>
-			<td align="center"><b>b / B / byteSent</b></td>
-			<td>
-				<p>
-					Response's content length.
-				</p>
-			</td>
-		</tr>				
-		<tr>
-			<td align="center"><b>h / clientHost</b></td>
-			<td>
-				<p>
-					Remote host.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td align="center"><b>H / protocol</b></td>
-			<td>
-				<p>
-					Request protocol.
-				</p>
-			</td>
-		</tr>
-    <tr>
-      <td align="center"><b>l</b></td>
-			<td>
-				<p>
-					Remote log name. In logback-access, this converter always
-					returns the value "-".
-				</p>
-			</td>
-		</tr>
-
-		<tr>
-			<td align="center"><b>reqParameter{paramName}</b></td>
-			<td>
-				<p>
-					Parameter of the response. This conversion word can be followed by a key 
-					whose corresponding data will be extracted from the header information.
-				</p>
-			</td>
-		</tr>		
-		<tr>
-			<td align="center"><b>i{header} / header{header}</b></td>
-			<td>
-				<p>
-					Request header. Just like the reqParameter
-					conversion word, reqParameter can be followed by a key.
-				</p>
-			</td>
-		</tr>	
-		<tr>
-			<td align="center"><b>m / requestMethod</b></td>
-			<td>
-				<p>
-					Request method.
-				</p>
-			</td>
-		</tr>		
-		<tr>
-			<td align="center"><b>r / requestURL</b></td>
-			<td>
-				<p>
-					URL requested.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td align="center"><b>s / statusCode</b></td>
-			<td>
-				<p>
-					Status code of the request.
-				</p>
-			</td>
-		</tr>		
-		<tr>
-			<td align="center"><b>t / date</b></td>
-			<td>
-				<p>
-					Date of the event.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td align="center"><b>u / user</b></td>
-			<td>
-				<p>
-					Remote user.
-				</p>
-			</td>
-		</tr>		
-		<tr>
-			<td align="center"><b>U / requestURI</b></td>
-			<td>
-				<p>
-					Requested URI.
-				</p>
-			</td>
-		</tr>		
-		<tr>
-			<td align="center"><b>v / server</b></td>
-			<td>
-				<p>
-					Server name.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td align="center"><b>localPort</b></td>
-			<td>
-				<p>
-					Local port.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td align="center"><b>reqAttribute{attributeName}</b></td>
-			<td>
-				<p>
-					Attribute of the request. Just like the reqParameter
-					conversion word, reqAttribute can be followed by a key.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td align="center"><b>reqCookie{cookie}</b></td>
-			<td>
-				<p>
-					Request cookie. Just like the reqParameter
-					conversion word, reqCookie can be followed by a key.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td align="center"><b>responseHeader{header}</b></td>
-			<td>
-				<p>
-					Header of the response. Just like the reqParameter
-					conversion word, responseHeader can be followed by a key.
-				</p>
-			</td>
-		</tr>
-		</table>
-				
+		
+		<p>
+			For detailled instructions on how to use the <code>PatternLayout</code> for
+			logback access, please refer to the 
+			<a href="manual/layouts.html#AccessPatternLayout">corresponding chapter</a> 
+			of the logback manual.
+		</p>
+		
 		<h2>JMX Components</h2>
 		
 		<p>Logback access easily integrates with JMX servers to publish useful information



More information about the logback-dev mailing list