At 3:20 PM -0500 8/25/05, Hubert Rabago wrote:
(Moving to dev.)
I already started to take a look at this sometime ago. (In fact, I
had to make sure I didn't check in changes I shouldn't while I was
working on those deprecations.) The thing I ran into was, the result
I'd get wasn't always fully reliable. If a forward of an action had a
problem, for instance, the line number I'd get would sometimes be the
one where the closing </action-mappings> tag was at.
It may be that the reliability of the line number we get would depend
on the SAX parser implementation in use.
I'm sure that's part of it -- but in my book, even just telling
people which file has the problem would help a lot; at least, in my
case, where we make a myriad of config files to make things easier to
manage. There are also probably just rules of XML such that the
parser may legitimately consider the problem to be someplace other
than where you do -- but it would still be better than nothing.
And the other thing, were we could add context and experience to
"interpret" exceptions thrown from libraries instead of just passing
them through or lightly wrapping them -- that could do a huge amount
for usability.
Joe
--
Joe Germuska
[EMAIL PROTECTED]
http://blog.germuska.com
"Narrow minds are weapons made for mass destruction" -The Ex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
