Antwort: Re: Entity Resolver and Xerces 1.4.1

In my opinion one advantage of the entity resolver is the ability to pass in the grammar direct as a stream. But using precompiled grammars sounds still better. About my proposing: The method description does not allow the resolving of grammar URIs. The class description allows it. So what I me

Antwort: Re: [Xerces2] Design Decisions (LONG)

Hi, it was a misunderstanding. If you only have spoken about internal Interface please do not misunderstand my commnents. But may be that you are able to standardize the framework you want to build. Regards Thomas Andy Clark <[EMAIL PROTECTED]> am 04.07.2001 03:35:35 Bitte antworten an

XMLSchema:

Hi! All, I want to create a document which allows the instance to have any elements which the author wants to have in his document e.g. I would like the above schema to validate the following type of instance documents: I do not know what the creator of the document might use

Re: Entity Resolver and Xerces 1.4.1

[EMAIL PROTECTED] wrote: > This is in contrast to the method description of resolveEntity(): It doesn't seem to be in contrast. Just not as complete a comment as in the SAX JavaDoc. > In my opinion the first one should be the right one to allow > storing grammars in the database also. eh? Are

[Xerces2] PSVI

PSVI: "Post Schema Validation Infoset" This is going to throw a big wrench into the works, I fear. And what's worse is that as new standards are created that augment the document's infoset, there's no standard way of layering (or representing) the accumulation of these augmentations. (It's intere

Re: [Xerces2] Design Decisions (LONG)

[EMAIL PROTECTED] wrote: > you are absolutely right that there are some problems with SAX but it is > now a defacto industry standard. > So in my opinion SAX should be supported. I'm not removing the SAX parser from the standard Xerces2 codebase. But our *internal* interfaces currently rely on SA

[Bug 1764] - bug in whatCanGoHere() in SimpleContentModel

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1764 *** shadow/1764 Sun May 20 17:27:29 2001 --- shadow/1764.tmp.7 Tue Jul 3 14:12:31 2001 *** *** 1,19 ! Bug#: 1764 ! Product: Xerces-J ! Version: unspecified ! Platform: Other ! OS/Version: Other ! Status: NEW ! R

[Bug 1774] - Zero-length file causes SAX parser to halt execution of thread

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1774 *** shadow/1774 Sun May 20 17:27:33 2001 --- shadow/1774.tmp.9825Tue Jul 3 11:34:54 2001 *** *** 1,19 ! Bug#: 1774 ! Product: Xerces-J ! Version: 1.3.0 ! Platform: PC ! OS/Version: Windows NT/2K ! Status: NEW ! Re

[Bug 2421] - getProperty throws exception for "schemaLocation" and "noNamespaceSchemaLocation"

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2421 *** shadow/2421 Mon Jul 2 23:40:47 2001 --- shadow/2421.tmp.7784Tue Jul 3 08:05:03 2001 *** *** 2,9 | getProperty throws exception for "schemaLocation" and "noNamespaceSchemaLo | +---

[Bug 2434] - Crimson claims not to support features it does support

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2434 *** shadow/2434 Tue Jul 3 05:00:26 2001 --- shadow/2434.tmp.6193Tue Jul 3 05:01:48 2001 *** *** 14,17 | URL: | +=

[Bug 2434] New: - Crimson claims not to support features it does support

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2434 *** shadow/2434 Tue Jul 3 05:00:26 2001 --- shadow/2434.tmp.6097Tue Jul 3 05:00:26 2001 *** *** 0 --- 1,17 + ++ + | Crimson claims not

[Bug 2433] - Crimson supports string-interning, but claims not to

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2433 *** shadow/2433 Tue Jul 3 04:46:25 2001 --- shadow/2433.tmp.5688Tue Jul 3 04:48:33 2001 *** *** 19,22 through its SAX driver, for the convenience of client software. (Reported on Xerces-J, since there is no s

[Bug 2433] New: - Crimson supports string-interning, but claims not to

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2433 *** shadow/2433 Tue Jul 3 04:46:25 2001 --- shadow/2433.tmp.5675Tue Jul 3 04:46:25 2001 *** *** 0 --- 1,22 + ++ + | Crimson supports s

[Bug 2432] New: - null pointer exception parsing large document

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2432 *** shadow/2432 Tue Jul 3 03:04:13 2001 --- shadow/2432.tmp.5310Tue Jul 3 03:04:14 2001 *** *** 0 --- 1,31 + ++ + | null pointer excep

Entity Resolver and Xerces 1.4.1

Hi, What do you think about the folllowing to the implementation of the Entity Resolver: In the class description I have found the following: "The XML reader will then allow the application to intercept any external entities (including the external DTD subset and external parameter entities, i

Re: [Xerces2] Design Decisions (LONG)

Hi, you are absolutely right that there are some problems with SAX but it is now a defacto industry standard. So in my opinion SAX should be supported. I do not know Mr. Megginson. But may be there is a way to create something like SAX3 to produce widely accepted interfaces with more functionali