Details
-
Bug
-
Status: Reopened
-
Major
-
Resolution: Fixed
-
None
-
None
-
New, Patch Available
Description
HyphenationCompoundWordTokenFilter loads the DTD in its XML parser from memory by supplying EntityResolver. In Java 1.4 (affects Lucene 2.9, but also later versions if not Apache Xerces is used as XML parser) this does not work, because Cromson does not even ask the entity resolver, if no base URI is known. As the hyphenation file is loaded from Reader/InputStream no base URI is known. Crimson needs at least a non-null systemId to proceed.
This patch (Lucene 2.9 only) fakes this by supplying a fake systemId to the InputSource.
Attachments
Attachments
Issue Links
- is part of
-
LUCENE-2732 Fix charset problems in XML loading in HyphenationCompoundWordTokenFilter (also Solr's loader from schema)
- Closed