• Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.5
    • Fix Version/s: None
    • Labels:
    • Environment:

      Operating System: other
      Platform: Other


      While testing our application we ran into a strange Digester parse issue.
      It looks like the Digester sometimes forgets to parse a value in the xml. Here
      the situation:

      1. If we fire testscript A that doesnot comply to the schema we set on the
      Digester then we get a parsing error as expected. The error is that field Z in
      the xml was not valid.
      2. We fire testscript B which should return an answer. The first time we fire
      it the Digester doesnot map field Z (which now has a valid value) to the java
      class as defined in the rule file.
      3. We fire testscript B again unchanged and now field Z is mapped by the
      Digester to the correct attribute in the corresponding java class.

      If at point 1 we dont fire testscript A (with the invalid value for attribute Z)
      but say C or any other this doesnot occur and we get the reply we expect......

      It seems like that after a call which results in a SAXException due to an
      invalid value in the XML according to the attached schema the next call fails
      to parse the xml correctly to the java object defined in the rule file. The
      third call however (which is exactly the same as the second) succeeds.

      Any idea's?

      Lars Vonk


        lars created issue -
        Henri Yandell made changes -
        Field Original Value New Value
        issue.field.bugzillaimportkey 29838 12341547
        Henri Yandell made changes -
        Component/s Digester [ 12311111 ]
        Assignee Jakarta Commons Developers Mailing List [ ]
        Affects Version/s 1.5 Final [ 12311664 ]
        Key COM-1395 DIGESTER-27
        Project Commons [ 12310458 ] Commons Digester [ 12310471 ]
        Henri Yandell made changes -
        Affects Version/s 1.5 Final [ 12311691 ]
        Henri Yandell made changes -
        Status Resolved [ 5 ] Closed [ 6 ]


          • Assignee:
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: