logging-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ggreg...@apache.org
Subject svn commit: r1364282 - /logging/log4j/log4j2/trunk/api/src/main/java/org/apache/logging/log4j/message/Message.java
Date Sun, 22 Jul 2012 12:44:40 GMT
Author: ggregory
Date: Sun Jul 22 12:44:39 2012
New Revision: 1364282

URL: http://svn.apache.org/viewvc?rev=1364282&view=rev
Add missing Javadoc paragraph markers.


Modified: logging/log4j/log4j2/trunk/api/src/main/java/org/apache/logging/log4j/message/Message.java
URL: http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/api/src/main/java/org/apache/logging/log4j/message/Message.java?rev=1364282&r1=1364281&r2=1364282&view=diff
--- logging/log4j/log4j2/trunk/api/src/main/java/org/apache/logging/log4j/message/Message.java
+++ logging/log4j/log4j2/trunk/api/src/main/java/org/apache/logging/log4j/message/Message.java
Sun Jul 22 12:44:39 2012
@@ -23,12 +23,13 @@ import java.io.Serializable;
  * around Objects so that user can have control over converting Objects to Strings when necessary
  * requiring complicated formatters and as a way to manipulate the message based on information
  * at runtime such as the locale of the system.
- *
+ *<p>
  * Note: Message objects should not be considered to be thread safe nor should they be assumed
to be
  * safely reusable even on the same thread. The logging system may provide information to
the Message
  * objects and the Messages might be queued for asynchronous delivery. Thus, any modifications
to a
  * Message object by an application should by avoided after the Message has been passed as
a parameter on
  * a Logger method.
+ * </p>
  * @doubt Interfaces should rarely extend Serializable according to Effective Java 2nd Ed
pg 291.
  * (RG) That section also says "If a class or interface exists primarily to participate in
a framework that
  * requires all participants to implement Serializable, then it makes perfect sense for the
class or

View raw message