vmote 2003/07/07 10:01:45
Modified: src/documentation/content/xdocs/dev conventions.xml
Log:
Include missing URL missed in translation from wiki.
Revision Changes Path
1.3 +1 -1 xml-fop/src/documentation/content/xdocs/dev/conventions.xml
Index: conventions.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/conventions.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- conventions.xml 1 Jul 2003 18:40:26 -0000 1.2
+++ conventions.xml 7 Jul 2003 17:01:45 -0000 1.3
@@ -82,7 +82,7 @@
<li>Avoid using exceptions for flow control.</li>
<li>Try to catch exceptions as much as possible and rethrow higher level
exceptions (meaning hiding the low level detailed and putting a message that is more
related to the function of your code).</li>
<li>It is important not to lose the stack trace which contains important
information.
-Use chained exception for that. Avalon Framework provides [CascadingException] (and
similar) for this.
+Use chained exception for that. Avalon Framework provides <jump
href="http://jakarta.apache.org/avalon/api/org/apache/avalon/framework/CascadingException.htm";>CascadingException</jump>
(and similar) for this.
Exception class names and stack traces must be treated like gold.
Do whatever is required so that this information is not lost.
Printing error messages to System.err or System.out is useless in a server-side
environment where this info is usually lost.</li>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
