xmltool

Updates: Status: GitHub Comment #5 on issue 40 by mathieu....@gmail.com: set doctype http://code.

Comment #5 on issue 39 by mathieu....@gmail.com: document.normalize in multi-thread env has

Updates: Status: Closed Comment #1 on issue 37 by mathieu....@gmail.com: Gros refactor - standardiser

Updates: Status: GitHub Comment #3 on issue 36 by mathieu....@gmail.com: Provide a virtual node

Updates: Status: GitHub Comment #3 on issue 35 by mathieu....@gmail.com: how to insert a tag using

Updates: Status: Closed Comment #2 on issue 34 by mathieu....@gmail.com: Namespace management http://

Updates: Status: GitHub Comment #1 on issue 33 by mathieu....@gmail.com: provide constructors with

Comment #4 on issue 41 by auste...@gmail.com: Handling the "Content not allowed in prolog"

Thank you Mathieu, In the mean time, I have thought of rolling my own API, that mimicks that of

notification test

Status: New Owner: mathieu....@gmail.com New issue 38 by mathieu....@gmail.com: notification test

Mathieu wrote: > the trick would be to create another XMLTag in an existing one This solution

No there's no such thing yet. If you need it, you can checkout the trunk of xmltool and add a

Mathieu wrote: > You must always use namepsaces in your xpath expressions (this > limitation

Yes true. When you create a namespace-aware node, it remains namespace- aware. I also had the same

Comment by oliver.schrenk: The Link to the test/example code using raw XPath expressions dosen't

Updates: Status: Fixed Comment #1 on issue 16 by mathieu.carbou: Remove all deprecations http://code.

Updates: Labels: -Milestone-Release3.0 Comment #3 on issue 19 by mathieu.carbou: documentation /

Comment #13 on issue 13 by mathieu.carbou: add api to clone XMLTag instance http://code.google.com/p/

Updates: Status: WontFix Labels: -Type-Defect -Priority-Medium Comment #1 on issue 30 by mathieu.

Comment #3 on issue 29 by golimpio: More iteration abilities http://code.google.com/p/xmltool/issues/

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

Updates: Status: Deployed Comment by mathieu.carbou: Deployed in Maven repository Affected issues:

Updates: Labels: -Milestone-Release3.0 Comment #7 on issue 20 by mathieu.carbou: Use dom4j / jaxen

Updates: Status: Fixed Comment #1 on issue 28 by mathieu.carbou: Adding methods http://code.google.

Updates: Status: Fixed Comment #1 on issue 27 by mathieu.carbou: Remove namespaces http://code.google

Updates: Status: Deployed Comment by mathieu.carbou: (No comment was entered for this change.)

Updates: Status: Deployed Comment #3 on issue 26 by mathieu.carbou: Add set* methods for text and

Updates: Status: Fixed Labels: -Milestone-Release3.0 Milestone-Release2.10 Comment #1 on issue 22 by

Updates: Status: Fixed Comment #2 on issue 26 by mathieu.carbou: Add set* methods for text and cdata