Filip Jirsák comments

Results 23 comments of


                                            Filip Jirsák

Variables in modules do not end up in the global object/scope, so you can't access them via context.getBindings("js")

I think it is right that the variables are not in the global scope. This is the meaning of modules. I consider it a mistake that the exported variables and...

Preserve Empty Lines

Hello @haruntuncay , pull requests are welcome :-) I'll assign this issue to you, can I?

Sorting of element attributes

@PAX523 Pull requests are welcome. Thank you!

Correct work with weak references in QNameCache

`QNameCache` is used to reduce the number of `QName` instances created - it is assumed that only a limited set of `QName`s will be used. If you have a lot...

Dom4j 2.1.1 has regression and is stripping entities

@vmassol Default behavior changed only for `DocumentHelper.parseText()`. I think this issue is related more likely with #44, but the only difference I see in the debugger is that feature `http://apache.org/xml/features/nonvalidating/load-external-dtd`...

element.getTextTrim() have a use problem

I don't understand what the problem is.

XPath – text() should use normalization

@reluxa This is correct, there can be multiple adjacent text nodes. You can call `document.normalize()` to settle text nodes. This issue is about XPath matching - normalization should probably be...

Recursive dependency on jaxen

It is necessary to separate Jaxen dependent classes into a separate module. I will split dom4j into modules in version 3.0.

Recursive dependency on jaxen

Jaxen dependency marked optional. It is not a solution to this problem, but it is one step towards it :-)

Xpp fixes

dom4j 2.1.x branch stay on `pull-parser:pull-parser:2` and `xpp3:xpp3:1.1.4c` versions. Move to `pull-parser:pull-parser:2.1.10` and `org.ogce:xpp3:1.1.6` is incompatible change, I schedule it to dom4j 3.0.