[jira] Reopened: (XERCESC-1690) endElement called before startElement

["Rick O'Shea (JIRA)" <xe...@xml.apache.org>]

     [ https://issues.apache.org/jira/browse/XERCESC-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick O'Shea reopened XERCESC-1690:
----------------------------------


Sorry for reopening this...but I really am still seeing an issue here.

In my overridden startElement & endElement code, I output some simple debug text to inform me about which xml element it is parsing.

When I have xml such as this:

      <aNode name="main">
        <event name="repair" />
      </aNode>

...the debug output tells me:

startElement : aNode
endElement : event
startElement : event
endElement : aNode

I am aware of the isEmpty flag, but this still does not explain the bizarre premature call to endElement. As it happens, this is not critical to my code, hence the "minor" priority  :-)  But it is certainly not the behavior I would expect.

> endElement called before startElement
> -------------------------------------
>
>                 Key: XERCESC-1690
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1690
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Validating Parser (DTD)
>    Affects Versions: 2.7.0
>         Environment: Fedora Core 1 - 6
> GCC
>            Reporter: Rick O'Shea
>            Priority: Minor
>
> I have derived a new parser class from XercesDOMParser, and overridden the startElement & endElement callbacks.
> All seems well...except I have noticed that when my XML contains empty-element tags "/>" ...
> eg.  <element name=value />
> ...the endElement callback is called first!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org