Even tough I see how this can be more useful I hate to think about the performance implications. With the line and column information all we are doing is just reporting the scanner information since we are using the org.apache.xerces.readers.DefaultEntityHandler getLineNumber() and getColumnNumber() methods.
What you are proposing is modifying the implementation of the
Locator interface ( LocatorImpl) and maybe modifying the
org.apache.xerces.framework.XMLParser reportError method.
By the way all the error error reporting originates here at reportError method of class XMLParser.
Do you have an implementation?
Thanks,
Jeffrey Rodriguez
XML Development
IBM CupertinoFrom: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [PROPOSAL] new LocatorImpl methods and/or SchemaMessages changes Date: Fri, 25 Feb 2000 12:37:24 -0500
One of the things I need from the schema implementation is details on exactly where an error occurs (over and above the line number). For instance, the message "[Error] :5:66: Incorrect datatype: A is not a boolean." isn't too helpful if I can't access the document via the line number. Basically, what I'd like is the name of the element and (if applicable) the attribute that's causing the problem. As far as I can tell, there are two ways to do this: (1) modify the error messages and the methods that call the error reporting methods, and/or (2) modify LocatorImpl() so that it has setElementName(), getElementName(), setAttributeName(), and getAttributeName() methods (and update these values accordingly).
Does anyone have input on what would be the preference (or if neither of them are appealing)?
Kito D. Mann Virtua Communications Corp
______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com
