[
https://issues.apache.org/jira/browse/DERBY-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925656#comment-13925656
]
Knut Anders Hatlen commented on DERBY-1997:
-------------------------------------------
In most cases I believe that going through the chain using getNextException()
isn't going to give more information than printStackTrace(), but there still
are some cases where printStackTrace() won't show all exceptions that
getNextException() would. That's typically when Derby continues processing
after an error, and reports all errors at the end. See for example
SystemProcedures.rollBackAndThrowSQLException().
> Misleading text in WwdEmbedded demo source file for Working With Derby
> ----------------------------------------------------------------------
>
> Key: DERBY-1997
> URL: https://issues.apache.org/jira/browse/DERBY-1997
> Project: Derby
> Issue Type: Bug
> Components: Demos/Scripts, Documentation
> Affects Versions: 10.2.1.6
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
> Labels: derby_triage10_5_2
> Attachments: DERBY-1997.diff, DERBY-1997.stat,
> vcs-diff3523819486798216332.patch, vcs-diff7276709987551559550.patch
>
>
> I'm making some minor fixes to the Working With Derby manual (DERBY-1948,
> DERBY-1972). The description of the WwdEmbedded.java program in the HTML
> generated from the file rwwdactivity3.dita
> (http://db.apache.org/derby/docs/dev/workingwithderby/) contains the
> following paragraph:
> DERBY EXCEPTION REPORTING CLASSES: The two methods at the end of the file,
> errorPrint and SQLExceptionPrint, are generic exception reporting routines
> that can be used with any JDBC program. This type of exception handling is
> required because often multiple exceptions (SQLException) are chained
> together then thrown. A while loop is used to report on each error in the
> chain. These classes are used by calling the errorPrint method from the catch
> block of the code that accesses the database.
> The introductory text "DERBY EXCEPTION REPORTING CLASSES" is keyed to a
> comment with the same text in the
> DERBY_HOME/demo/programs/workingwithderby/WwdEmbedded.java program:
> // ## DERBY EXCEPTION REPORTING CLASSES ##
> /*** Exception reporting methods
> ** with special handling of SQLExceptions
> ***/
> The problem is that there are no Derby exception reporting classes, only
> methods, as far as I can tell. The use of the term CLASSES is likely to
> confuse any users not well acquainted with Java (one of the target audiences
> of this manual). It would be great if someone could change CLASSES to METHODS
> in the WwdEmbedded.java file so that I can make the corresponding fix to the
> rwwdactivity3.dita file. I would also have to correct the confusing last
> sentence of the paragraph; I think it would make more sense to say, "The
> program starts this process by calling the errorPrint method from the catch
> block of the code that accesses the database." (I can't just change "classes"
> to "methods" because errorPrint *is* one of the methods.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
