[kaffe] Re: [Classpathx-xml] Unwanted SAXParseException

2003-10-18 Thread David Brownell
Ito Kazumitsu wrote: private static class MyResolver implements EntityResolver { public InputSource resolveEntity (String publicId, String systemId) { try { return new InputSource((new URL(systemId)).openStream()); This is the bug right here ... you're creating an InputSource wit

[kaffe] Re: [Classpathx-xml] Unwanted SAXParseException

2003-10-18 Thread David Brownell
The basic issue is that applying _any_ heuristic at that level is going to fail badly in some cases. Throwing an exception is at least an indication that the inputs were bad. And AElfred2 was at least reporting a warning about what was wrong, before throwing the exception. In situations like t

[kaffe] Re: [Classpathx-xml] Unwanted SAXParseException

2003-10-18 Thread David Brownell
Arnaud Vandyck wrote: On Sat, 18 Oct 2003 08:21:35 -0700 David Brownell <[EMAIL PROTECTED]> wrote: That's part of the reason why the SAX spec has long said specifically: "An InputSource object belongs to the application: the SAX parser shall never modify it in any way...". (Which is what your pat

[kaffe] CVS kaffe (kaz): libraries/javalib/gnu/xml/aelfred2/SAXDriver.java:

2003-10-18 Thread Kaffe CVS
PatchSet 4114 Date: 2003/10/19 02:31:53 Author: kaz Branch: HEAD Tag: (none) Log: 2003-10-19 Ito Kazumitsu <[EMAIL PROTECTED]> * libraries/javalib/gnu/xml/aelfred2/SAXDriver.java: Reverted because the 2003-10-18 change was unreasonable. Members: ChangeLog:1.1708->1.170

[kaffe] (no subject)

2003-10-18 Thread Ito Kazumitsu
> "*" == Ito Kazumitsu <[EMAIL PROTECTED]> writes: *> Giving the warning of "missing system ID" should be postponed *> until the system ID is really needed. *> *> And here is my patch: With this patch, and without the previvous patch, my test case goes like this: bash-2.05b$ java TestEntit

[kaffe] Re: [Classpathx-xml] Unwanted SAXParseException

2003-10-18 Thread Ito Kazumitsu
> ":" == David Brownell <[EMAIL PROTECTED]> writes: :> Ito Kazumitsu wrote: >> private static class MyResolver implements EntityResolver { >> public InputSource resolveEntity (String publicId, String systemId) { >> try { >> return new InputSource((new URL(systemId)).openStream()); :> This is

[kaffe] Re: [Classpathx-xml] Unwanted SAXParseException

2003-10-18 Thread Nic Ferrier
David Brownell <[EMAIL PROTECTED]> writes: > Arnaud Vandyck wrote: > > On Sat, 18 Oct 2003 08:21:35 -0700 > > David Brownell <[EMAIL PROTECTED]> wrote: > > > > > >>That's part of the reason why the SAX spec has long said specifically: > >>"An InputSource object belongs to the application: the SA

[kaffe] Re: [Classpathx-xml] Unwanted SAXParseException

2003-10-18 Thread Arnaud Vandyck
On Sat, 18 Oct 2003 08:21:35 -0700 David Brownell <[EMAIL PROTECTED]> wrote: > That's part of the reason why the SAX spec has long said specifically: > "An InputSource object belongs to the application: the SAX parser > shall never modify it in any way...". (Which is what your patch > makes it do

[kaffe] win32: glitch in winthread.c:setpriority

2003-10-18 Thread Marc Kleine-Budde
Hello! I don't know if this peace of code is in use, but I found a missing 'break' statement in win32's setpriority code: bye - Marc -- #!/bin/sh set - `type $0` 'tr "[a-zA-Z]" "[n-za-mN-ZA-M]"';while [ "$2" != "" ];do \ shift;done; echo 'frq -a -rc '`echo "$0"| $1 `'>$UBZR/.`rpub signature|'`\

[kaffe] Re: [Classpathx-xml] Unwanted SAXParseException

2003-10-18 Thread Arnaud Vandyck
On Sat, 18 Oct 2003 08:59:20 +0900 Ito Kazumitsu <[EMAIL PROTECTED]> wrote: > I found a case where GNU JAXP throws unwanted SAXParseExceptions. > The test case is attached below. When using Sun's JAXP or > Xerces, such exceptions are not thrown. > > Also attached is my suggested patch, which I