Marc4j Exception Handling

[GoogleCodeExporter]

When the marc4j find an error while parsing records from "flat" MARC format
to Record object it stops the parsing method, and we don't have enough
information to identify the record in question. We should see the method
marc4j use, and maybe modify it, to get at least the control number, or -
better - the MARC format to put it into error stream.

The marc4j exception's message does not  always gives us the real reason. I
created an ExceptionPrinter class, which iterate through the error stack
and try to extract all information. This gives a better, but still human
ununderstandable message.

Original issue reported on code.google.com by shreyans...@gmail.com on 12 Mar 2009 at 7:11

[GoogleCodeExporter]

Original comment by sva...@library.rochester.edu on 7 Apr 2009 at 1:40

• Changed state: Started

[GoogleCodeExporter]

Original comment by sva...@library.rochester.edu on 19 May 2009 at 7:48

• Changed state: NotReleased

[GoogleCodeExporter]

The bug has been fixed, released and is incorporated in the 0.6 version of the 
OAI 
Toolkit.

Original comment by sva...@library.rochester.edu on 26 May 2009 at 7:25

• Changed state: Done