| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
are required to compile Xalan sources. committing these files on 'master' as well
…er. this makes it little bit easier to view xalanj xslt transformation result. doing this xalanj codebase change on 'master' branch. the previous commit, did this codebase change on xalanj branch xalan-j_xslt3.0.
Comments in file.
Revert default indent-amount
…change that was done earlier : movement of the 2.7.3_release test cases to jira directory. also making a minor improvement to error handling within xalanj implementation codebase, when variables were not been resolved within an xslt 1.0 stylesheet.
committing minor changes to xalanj README file, as per the following change that was done earlier : movement of the 2.7.3_release test cases to jira directory. also making a minor improvement to error handling within xalanj implementation codebase, when variables were not been resolved within an xslt 1.0 stylesheet.
…alling `parse(Node)`, calls the `ContentHandler`'s `startDocument` and `endDocument`, since `parse()` won't call them in this case; `parse(InputSource unused)` just calls `parse(Node)`, so the `ContentHandler` does not gereceive the `startDocument` and `endDocument` events, which are mandated by the SAX specification. This can cause problems; see, for example, scala/scala-xml#694 The simplest way to fix this is to change `parse(InputSource unused)` to call `parse()` instead of `parse(Node)` - and this is what this pull request does.
|
Sorry for the delay in processing this. With all the changes made since then, the simplest and safest way to apply this seemed to be to cherry-pick the one file you altered rather than updating/reconciling/merging. I've done so. As I understand it, Git should have retained your credit on the change. Good catch, simple solution. Thanks! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
For DOM that is not a Document, DOM2SAX.parse(), in addition to calling parse(Node), calls the ContentHandler's startDocument and endDocument, since parse() won't call them in this case; parse(InputSource unused) just calls parse(Node), so the ContentHandler does not gereceive the startDocument and endDocument events, which are mandated by the SAX specification.
This can cause problems; see, for example, scala/scala-xml#694
The simplest way to fix this is to change parse(InputSource unused) to call parse() instead of parse(Node) - and this is what this pull request does.