You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-commits@xmlgraphics.apache.org by pb...@apache.org on 2002/05/07 18:31:45 UTC
cvs commit: xml-fop/src/org/apache/fop/messaging MessageHandler.java
pbwest 02/05/07 09:31:44
Modified: src/org/apache/fop/messaging Tag: FOP_0-20-0_Alt-Design
MessageHandler.java
Log:
Reformatted
Revision Changes Path
No revision
No revision
1.5.2.1 +16 -11 xml-fop/src/org/apache/fop/messaging/Attic/MessageHandler.java
Index: MessageHandler.java
===================================================================
RCS file: /home/cvs/xml-fop/src/org/apache/fop/messaging/Attic/MessageHandler.java,v
retrieving revision 1.5
retrieving revision 1.5.2.1
diff -u -r1.5 -r1.5.2.1
--- MessageHandler.java 30 Jul 2001 20:29:29 -0000 1.5
+++ MessageHandler.java 7 May 2002 16:31:44 -0000 1.5.2.1
@@ -15,25 +15,28 @@
* The class MessageHandler contains the static methods log and error which
* should be used for any end user information instead of System.out.print() or
* System.err.print(). The class defines several output methods:
- * writing to the screen (default), logging to a file, creating message events and repressing all
- * output. If you don't want to change the default behaviour, you should be
+ * writing to the screen (default), logging to a file, creating message events
+ * and repressing all output.
+ * If you don't want to change the default behaviour, you should be
* happy with MessageHandler.log(message) and MessageHandler.error(message)<br>
- * The class MessageHandler also supports the setting of an id. If set every message
- * has as a prefix an identifying string. That way Fop probably can also be used in
- * environments, where more than one Fop instance are running in same JVM.<br>
+ * The class MessageHandler also supports the setting of an id.
+ * If set every message has as a prefix an identifying string.
+ * That way Fop probably can also be used in
+ * environments where more than one Fop instance are running in same JVM.<br>
* If Fop is embedded in a gui application or for any reasons the existing
* messaging system doesn't meet the programmer's requirements, one can add
* a MessageEvent listener to MessageHandler and handle the incoming messages
- * in an appropriate way. See the class DefaultMessageListener, which is a trivial
- * implementation of the MessageListener.
- * Here is an example how to configure MessageHandler for the DefaultMessageListener (anybody
+ * in an appropriate way. See the class DefaultMessageListener, which is a
+ * trivial implementation of the MessageListener.
+ * Here is an example how to configure MessageHandler for the
+ * DefaultMessageListener (anybody
* can provide his own listener by extending MessageListener<br>
* <code>
* MessageHandler.setOutputMethod(MessageHandler.EVENT);
* MessageHandler.addListener(new DefaultMessageListener());
* </code><br>
- * This examples shows, how to redirect the messages to a log file called fop.log.
- * All messages are appended to this file.
+ * This examples shows how to redirect the messages to a log file called
+ * fop.log. All messages are appended to this file.
* <code>
* MessageHandler.setOutputMethod(MessageHandler.FILE);
* MessageHandler.setLogfileName("\\fop.log",true);
@@ -104,7 +107,9 @@
setMessage(message);
Enumeration enum = listeners.elements();
while (enum.hasMoreElements()) {
- ((MessageListener)enum.nextElement()).processMessage(new MessageEvent(getMessage()));
+ ((MessageListener)enum.nextElement()).processMessage(
+ new MessageEvent(getMessage())
+ );
}
break;
case NONE:
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-cvs-help@xml.apache.org