Summary: | "Fatal Error" gets written to System.err | ||
---|---|---|---|
Product: | POI | Reporter: | Christian Kohlschutter <christian> |
Component: | XSSF | Assignee: | POI Developers List <dev> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All |
Description
Christian Kohlschutter
2014-08-19 22:39:32 UTC
I'll leave one of our xml experts to decide on the best way to handle this However... Shared Strings tables are workbook wide, and can be read independently of any given sheet. As such, there's often no sheet object on hand to report an error through, so I'm not sure your suggested solution will work In Solr, we have http://lucene.apache.org/solr/4_9_0/solr-solrj/org/apache/solr/common/util/XMLErrorLogger.html This class is set as ErrorHandler when we setup the XMLReader. > As such, there's often no sheet object on hand to report an error through, so I'm not sure your suggested solution will work
But we can use the official logging framework of POI, like in Solr.
But as this is a fatal error, you will get the Exception explaining the parse problem in your calling code, so where is the problem?
I tried to reproduce this with the latest 4.0.0-SNAPSHOT version but could not, maybe some of the changes that we did over time already fixed this. If you still see this, please provide a small unit-test which shows the problem so we can more easily reproduce and fix it. |