Issue 20 in xmltool: Use dom4j / jaxen instead of JDK w3c dom implementation ?

[codesite...@google.com]

Comment #8 on issue 20 by golimpio: Use dom4j / jaxen instead of JDK w3c
dom implementation ?
http://code.google.com/p/xmltool/issues/detail?id=20

I have migrated a small project from DOM4J to XMLTool and I didn't find any
situation
where DOM4J was better than XMLTool.

In fact, there was only one situation where I'd prefer have used iteration
instead of
"foreach + callback". That's because using inline callback I'm not able to
access the
local method variables (except for final ones), and it makes me write more
code and
create unnecessary class attributes.

An option to have some kind of iteration for reading XML documents would be
useful
for some situations.

Thanks for your good work.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Updates:
Labels: -

Comment #9 on issue 20 by mathieu.carbou: Use dom4j / jaxen instead of JDK

w3c dom implementation ?
http://code.google.com/p/xmltool/issues/detail?id=20

Thank you for your report !

Yes for the current implemented features, dom4j won't bring more. For other
iteration
abilities, i have some ideas. I opened a new issue for that.

[codesite...@google.com]

Comment #10 on issue 20 by mathieu.carbou: Use dom4j / jaxen instead of JDK

w3c dom implementation ?
http://code.google.com/p/xmltool/issues/detail?id=20

Note:

Added method getChilds() and getChilds(xpath) to create an iterable object
over
selected elements.

Example:

for (XMLTag xmlTag : tag.getChilds()) {
System.out.println(xmlTag.getCurrentTagName());