 | | | XMLParseException changes and creation of XMLLocator2 | XMLParseException changes and creation of XMLLocator2 2004-08-30 - By Ankit Pasricha
>What does you return if the implementation does not support
>reporting of the character offset?
I think we can return -1 if not supported. This is consistent with what is
returned in the case of line/column number.
Ankit Pasricha
XML Parser Development
IBM Toronto Lab
8200 Warden Avenue, Ontario L6G 1C7
Phone: (905) 413 4941
Andy Clark
<andy@(protected)
et> To
xerces-j-dev@(protected)
08/30/2004 07:01 cc
PM
Subject
Re: [XNI CHANGE PROPOSAL]
Please respond to XMLParseException changes and
xerces-j-dev@(protected) creation of XMLLocator2
apache.org
Michael Glavassevich wrote:
> Here's a summary of the changes we've discussed:
>
> 1) Add a getCharacterOffset method to XMLLocator which returns the
> character offset for the current entity.
What does you return if the implementation does not support
reporting of the character offset?
> 2) Add a getVersion method to XMLLocator which returns the XML version
> of the current entity.
Why not "getXMLVersion" to match SAX2?
> 3) Add a getCharacterOffset method to XMLParseException to expose the
> offset from the XMLLocator.
Just curious: you are exposing the XML version through the
XMLLocator but *not* from the parse exception? I'm not in
favor of adding it; I was just curious.
> If people are comfortable with these changes, I'll make the updates in
CVS.
Seems fine to me.
--
Andy Clark * andyc@(protected)
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-dev-help@(protected)
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-dev-help@(protected)
|
|
|
