XMLParseException changes and creation of XMLLocator2 2004-08-26 - By Ankit Pasricha
The reason for creating a new interface was to not break anyone
implementing XMLLocator.
However, since it does not seem like we have too many implementations of
that interface around today,
It might be a better idea to stick this method in the same interface and
avoid the confusion of an XMLLocator2.
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/26/2004 02:17 cc
PM
Subject
Re: [XNI CHANGE PROPOSAL]
Please respond to XMLParseException changes and
xerces-j-dev@(protected) creation of XMLLocator2
apache.org
Ankit Pasricha wrote:
> The two code changes are listed below:
>
> XMLLocator2 extends XMLLocator {
>
> public int getCharacterOffset();
> }
Why are you extending the interface instead of just adding the
method to the existing interface?
I know I'd have to update some of my XNI tools to add the method
but that XMLLocator2 just sticks out like a sore thumb. Especially
since it's the only interface that uses this naming convention. And
it's not the approach we've used in the past to update XNI interfaces
-- previously, we just changed the original interface.
This type of change is a lot more graceful than when we went from
start/endPrefixMapping to passing a namespace context object to the
startDocument method...
--
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)
|
|
