Rolf Lear

Good catch. And appreciate the patch... but I am not particularly happy with the fix.... I think there's an issue in it: ``` if (previousCDATA != inCDATA || (ch[start] ==...

I am going to contemplate this issue for a bit. I think I may have an alternative approach which is more reliable. I will have to take the time to...

Just so you are aware, this issue is not a problem in JDOM 2.x , and I strongly recommend you upgrade to that. It is unlikely that there will be...

This was not done intentionally, it's a transfer from 1.x version: https://github.com/hunterhacker/jdom/blob/jdom-1.1/core/src/java/org/jdom/transform/XSLTransformer.java#L133 This needs some consideration as to whether changing it now would pose a compatibility risk. Is there a...

Hi Arnaud There are currently no bugs open against 1.1.x versions of JDOM. I understand that this is a usability problem, but I am not inclined to create a whole...

There is one workaround which has some promise, but I have not tried it because even if it _does_ work, it will not work in a simple enough way to...

As you can tell @kpopovic , this issue is relatively old , but incorporating Saxon support for >XPath1 support is still a "good idea". I originally worked with the Saxon...

Comprehensive list of JSON 'dialects' - http://wiki.open311.org/index.php?title=JSON_and_XML_Conversion

Include a 'auto-fail' resolver that always fails to allow faster errors if the network is down....

It's true that parsing the entire DOM consumes memory. On the other hand, in instances where memory is a problem, traditional SAX building and processing just the events would be...