Groovy
  1. Groovy
  2. GROOVY-5362

XmlParser and XmlSlurper should merge

    Details

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

      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

        Mark Thomas made changes -
        Workflow jira [ 12971717 ] Default workflow, editable Closed status [ 12979535 ]
        Mark Thomas made changes -
        Project Import Mon Apr 06 02:11:23 UTC 2015 [ 1428286283443 ]
        Mark Thomas made changes -
        Workflow jira [ 12734285 ] Default workflow, editable Closed status [ 12746000 ]
        Mark Thomas made changes -
        Field Original Value New Value
        Project Import Sun Apr 05 13:32:57 UTC 2015 [ 1428240777691 ]
        Hide
        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
        Hide
        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 )
        Russel Winder created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Russel Winder
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:

              Development