[ http://nagoya.apache.org/jira/browse/XERCESJ-1034?page=history ]
Michael Glavassevich resolved XERCESJ-1034:
-------------------------------------------
Resolution: Invalid
XIncludeHandler is only used by the XIncludeParserConfiguration. The config in
XInculdeHandler is internal and not meant to be configurable. The fact that
there are multiple parsers is just an artifact of the design.
> XIncludeHandler uses default parser configuration for included files
> --------------------------------------------------------------------
>
> Key: XERCESJ-1034
> URL: http://nagoya.apache.org/jira/browse/XERCESJ-1034
> Project: Xerces2-J
> Type: Bug
> Components: XInclude 1.0
> Versions: 2.6.2
> Reporter: Erik Bruchez
>
> In XIncludeHandler, find the line:
> String parserName = XINCLUDE_DEFAULT_CONFIGURATION;
> If you specified a different parser configuration using the property
> org.apache.xerces.xni.parser.XMLParserConfiguration, it is not taken into
> account for included files.
> I suggest the following patch:
> String parserName =
> System.getProperty("org.apache.xerces.xni.parser.XMLParserConfiguration");
> if (parserName == null)
> parserName = XINCLUDE_DEFAULT_CONFIGURATION;
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
