>The only problem is the same as with the standard SAX callbacks - the
>start entity tends not to come at the start of the entity reference,
>but at the start of the declaration which contains it.
I guess I don't understand this comment since the examples that I was
providing show that you do get the startEntity where you are expecting.
You are correct that SAX has rules that throw some of these events
away because the SAX methods are defined to do so, but all the events
native in Xerces are unfiltered and available for your use.
>What I'm really looking for is a way to get the unresolved string sent
>in the parameters for each callback.
How is that different than being able to do getProperty(".../xml-string")
in any callback to get that unresolved string ?
Regards,
Glenn
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
