Lines Matching full:logger
103 in the Logger interface accept message of type Object, but only
129 <code>org.slf4j.Logger</code> interface have methods for the
173 <li><a href="#declared_static"> Should Logger members of a class
203 logback exposes its logger API via SLF4J.
269 <code>org.slf4j.Logger</code> interface, pave the way for
548 code using <code>org.slf4j.Logger</code>,
779 printing methods in the Logger interface accept message of type
787 href="api/org/slf4j/Logger.html">Logger interface</a> were
816 <pre class="prettyprint source">logger.debug(new Exception("some error"));</pre>
846 <pre class="prettyprint source">logger.error("some accompanying message", e);</pre>
902 <p> For some Logger <code>logger</code>, writing,</p>
903 <pre class="prettyprint source">logger.debug("Entry number: " + i + " is " + String.valueOf(entry[i]));</pre>
916 <pre class="prettyprint source">if(logger.isDebugEnabled()) {
917 logger.debug("Entry number: " + i + " is " + String.valueOf(entry[i]));
923 <code>logger</code>. On the other hand, if the logger is
925 evaluating whether the logger is enabled or not, twice: once in
927 is an insignificant overhead because evaluating a logger takes
939 logger.debug("The entry is {}.", entry);</pre>
942 decision is affirmative, will the logger implementation format
955 <pre class="prettyprint source">logger.debug("The new entry is "+entry+".");
956 logger.debug("The new entry is {}.", entry);</pre>
960 href="apidocs/org/slf4j/Logger.html#debug(java.lang.String,%20java.lang.Object%2C%20java.lang.Object)">two
965 <pre class="prettyprint source">logger.debug("The new entry is {}. It replaces {}.", entry, oldEntry);</pre>
969 href="apidocs/org/slf4j/Logger.html#debug(java.lang.String%2C%20java.lang.Object...)"><code>Object...</code>
973 <pre class="prettyprint source">logger.debug("Value {} was inserted between {} and {}.", newVal, below, above);</pre>
1006 <pre class="prettyprint source">logger.debug("Set {1,2} differs from {}", "3");</pre>
1011 <pre class="prettyprint source">logger.debug("Set {1,2} differs from {{}}", "3");</pre>
1022 <pre class="prettyprint source">logger.debug("Set \\{} differs from {}", "3");</pre>
1033 <pre class="prettyprint source">logger.debug("File name is C:\\\\{}.", "file.zip");</pre>
1052 <pre class="prettyprint source">logger.debug("{}", complexObject);</pre>
1071 <code>org.slf4j.Logger</code> interface have methods for the FATAL
1086 <pre class="prettyprint">import org.slf4j.Logger;
1094 Logger logger = LoggerFactory.getLogger("aLogger");
1099 logger.error(<b>fatal</b>, "Failed to obtain JDBC connection", e);
1240 logger.error("Failed to format {}", s, e);
1245 href="http://www.slf4j.org/apidocs/org/slf4j/Logger.html#error%28java.lang.String,%20java.lang.Object,%20java.lang.Object%29">error
1283 logger, called say <code>MyLogger</code>, you need to provide
1285 <code>org.slf4j.Logger</code> interface. Refer to slf4j-jcl,
1317 <code>org.slf4j.Logger</code> interface
1354 methods in <code>org.slf4j.Logger</code> which take a
1420 <dt class="doAnchor" name="declared_static">Should Logger members
1446 <li>less memory overhead: logger declaration will
1492 <li>higher memory overhead: logger declaration will
1502 <p>Static logger members cost a single variable reference for
1503 all instances of the class whereas an instance logger member
1510 support a distinct logger context for each application running
1518 <p>More specifically, each time a logger is retrieved by
1522 <em>same</em> application retrieving a logger by a given name
1523 will always return the same logger. For a given name, a
1524 different logger will be returned only for different
1528 <p>If the logger is static, then it will only be retrieved once
1541 non-native SLF4J binding, will store logger instances in a map,
1542 short-circuiting context-dependent logger retrieval. For native
1551 <p><b>Logger serialization</b></p>
1554 serialized by default. As of SLF4J version 1.5.3, logger
1557 are declared as instance variables. In previous versions, logger
1563 <p>In summary, declaring logger members as static variables
1565 footprint. On the other hand, declaring logger members as
1568 possible to create a distinct logger environment for each
1586 recommended idiom for declaring a logger in a class?
1590 <p>The following is the recommended logger declaration
1596 import org.slf4j.Logger;
1600 <b>final (static) Logger logger = LoggerFactory.getLogger(MyClass.class);</b>
1605 part of the logger declaration, the above logger declaration
