[GROOVY-6274] replaceNode improvements for XML processing

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0-beta-1
• Fix Version/s: 2.2.0-beta-2
• Labels: breaking
• Assignee: Paul King
• Reporter: Paul King
• Created: 24/Jul/13 06:38
• Updated: 07/Apr/15 19:07
• Resolved: 24/Jul/13 20:12

Description

Groovy's XML processing has a few slightly inconsistent features and a small hole wrt replacing nodes.

The replaceNode(Closure) method for DOMCategory returns the last added node rather than the removed node (making it inconsistent with the built-in replaceChild method) and equivalent methods for general collections (e.g. remove for ArrayList).

Ditto for the corresponding method in XmlParser. Also, XmlParser lacks a replaceNode(Node) variant.