groovy

XmlParser and XmlSlurper should merge

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.0-beta-2
  • Fix Version/s: 2.x
  • Component/s: XML Processing
  • Labels:
    None
  • Number of attachments :
    0

Description

Currently there is XmlParser and XmlSlurper. They have essentially the same API and yet there are some noticeable differences that should be smoothed away. Moreover the difference between them should not be presented in terms of different classes, but should be merged behind a virtual constructor so that there is a single XmlParser class but different implementations with different runtime behaviours, i.e. the strict parser and the lazy parser.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Tim Yates added a comment -

It would be good if we could keep some of the differences available in the merged parser. ie: XmlParser maintains attribute ordering*, wheras XmlSlurper doesn't.

(* I realise attribute ordering is a weird one, but it is a requirement for some people)

Show
Tim Yates added a comment - It would be good if we could keep some of the differences available in the merged parser. ie: XmlParser maintains attribute ordering*, wheras XmlSlurper doesn't. (* I realise attribute ordering is a weird one, but it is a requirement for some people )
Hide
Permalink
Paul King added a comment -

There are possibly some lessons to be learned from the new JDom2 api:
http://hunterhacker.github.com/jdom/jdom2/apidocs/org/jdom2/input/sax/package-summary.html

Show
Paul King added a comment - There are possibly some lessons to be learned from the new JDom2 api: http://hunterhacker.github.com/jdom/jdom2/apidocs/org/jdom2/input/sax/package-summary.html

People

  • Assignee:
    Unassigned
    Reporter:
    Russel Winder
Vote (0)
Watch (3)

Dates

  • Created:
    Updated: