First, sorry it took so long to get around to reading this message. My
comments/questions are inline...
Andy Clark wrote:
>
> Everyone,
>
> Okay, I have added the scanner interfaces and made the changes
> to the Xerces2 reference implementation to implement this. I
> built it and ran it through the OASIS test suite. Nothing seems
> to have broken so I went ahead and committed the changes.
When you said you ran it through the OASIS test suite, what do you mean
by this? As I understand it the current tests at OASIS are broken and
there is a fixed version elsewhere, but it requires manually
interpreting over 1200 negative tests to verify passing those tests.
>
> This is actually quite cool because of the following reasons:
>
> 1) We can define a parser conifugration's pipeline dynamically.
> For example, through an XML config file or something. That
> way people could create new configurations (e.g. adding an
> XInclude filter in the pipeline) by tweaking the standard
> configuration file instead of having to create a new
> XMLParserConfiguration duplicating a lot of code.
Does this mean that Xerces 2 must read in and parse this config file
before parsing any source documents?
> Next, I'll be updating the XNI Manual in the documentation to
> detail these new interfaces. (I'll have to force myself 'cause
> I'm really feeling burnt out writing so much documentation. :)
> Anybody out there want to help with the documentation? We
> still need some docs on how to build parser configurations
> that use the Xerces2 standard components -- because they have
> certain dependencies, etc. So that's something that still
> needs to be done.
Did you get any takers? I'd like to get more familiar with this parser
config scheme so I may have some time to help out.
-Edwin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
