Hi Joe,
I guess I don't quite understand. The trouble is that the Locator2
implementation will, one way or another, live in our SAXParser class (or
more likely in the AbstractSAXParser, but same difference). An InputSource
containing some character stream could come at any time from a user's
EntityResolver, and this is never seen by anything past the
XMLEntityManager in the pipeline; that is, all information about that
character stream is lost long before the end of the pipeline where the
Locator2 impl lives.
So, if we're to support Locator2 precisely as its currently defined, it
seems inevitable that either (1) more info needs to get passed down the
pipeline via Augmentations or (2) XNI needs to accomodate the SAX
behaviour.
Did I miss something?
Cheers,
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: [EMAIL PROTECTED]
|---------+---------------------------->
| | Joseph |
| | Kesselman/Watson/|
| | [EMAIL PROTECTED] |
| | |
| | 03/03/2003 05:47 |
| | PM |
| | Please respond to|
| | xerces-j-dev |
| | |
|---------+---------------------------->
>---------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: treatment of encodings in XNI and SAX Locator2
|
|
|
|
|
>---------------------------------------------------------------------------------------------------------------------------------------------|
There's always the ugly solution: Support both views of the data, make the
SAX adapter layer call the method which matches its Locator2 behavior...
______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"may'ron DaroQbe'chugh vaj bIrIQbej" ("Put down the squeezebox and nobody
gets hurt.")
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
