[
https://issues.apache.org/jira/browse/XERCESC-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Massari resolved XERCESC-1690.
--------------------------------------
Resolution: Invalid
Sorry for the incorrect answer (I was mistakenly thinking you were using the
SAX handlers); if you are overriding the XercesDOMParser you should be aware
that its startElement callback will call the endElement callback if the isEmpty
flag is set to true (because the engine will not invoke endElement in that
case).
So if your derived method is first invoking the base class and then printing
the debug statement you will see the endElement trace printed before the
startElement one.
If your own code needs to be execute after the base class has created the DOM
node, but before the endElement has been executed, be sure to invoke the base
class with isEmpty=false, and then, if the original isEmpty is true, manually
invoke endElement
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
