Edwin Goei wrote:
> 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.
Basically, what I was trying to say is that after making the
change, I ran the test suite and compared the results with a
previous run of the test suite. A regression would have
affected the results. Yet the results were the same so that
led me to assume that my changes were a qualified "ok".
The IBM team has also been running it through their modified
test suite and seem pretty confident in the results. There
are a few more minor problems but it looks good for the most
part.
> Does this mean that Xerces 2 must read in and parse this config file
> before parsing any source documents?
No. I was only describing what *could* be done with the
new scanner definitions. Not what *is* done in the code
now. But by describing the configuration in an XML file,
we can do various things with it, including:
* actually read it in to build the standard configuration
* allow users to quickly and easily make custom configs
* write a tool that reads the parser configuration and
generate the code for that config
The last one seems more appropriate. Imagine a tool that
reads in your parser configuration description and then
generates the configuration class, and the JAXP impl that
will instantiate the various parsers using that config.
> 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.
Nope. I'd really appreciate any help you can offer in
this area. Let me know if you have any questions
regarding the components and their use.
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
