xml-commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Norman Walsh <...@nwalsh.com>
Subject CVS Resolver supports XML Catalogs 1.1
Date Wed, 13 Apr 2005 14:33:03 GMT
/ Norman Walsh <ndw@nwalsh.com> was heard to say:
| The XML Catalogs spec has been revised by the OASIS Entity Resolution
| Technical Committee. We've added two new entry types. As it turns out,
| one of them was the test case I used for extensibility, so it won't
| be hard to implement the new types :-)

I checked in the updated code this morning. The resolver now supports
systemIdSuffix and uriSuffix as defined in the XML Catalogs V1.1
Committee Specification.

And I added the bare beginnings of a JUnit test framework. I don't
really understand JUnit and Ant integration so I don't think it works
unless your CLASSPATH is setup right. I'd like to fix that,
suggestions welcome.

I also fixed (believe I've fixed :-) 8 of the 10 bugs that were
reported over the last (embarrassed gulp) several years.

I don't know how often the Commons work is packaged up for release,
but I'd sure appreciate feedback from others about the stability of
the new code before it gets shipped off in a real release.

I haven't really had a chance to investigate


and I think, though I can't verify, that I've fixed


confirmation one way or the other most gratefully accepted.

| Is there a process for rewrites? Suppose I spent some time working on
| it, what would I do with the result? Just check the refactored code in
| on top of the existing code? Put the new design in a branch? Put the
| old design in a branch? Give it a new set of package names? What's the
| Right Answer in xml-commons?

After giving it more thought, I think the right answer is to leave it
alone. No one is agitating for the rewrite and the classes are easy
enough to use in the common case.

I fear that changing the API in radical ways will just make everyone's
life harder and perhaps slow the deployment of Catalog support. That
seems like a high price to pay just to sweep some of my niave coding
under the rug.

That said, if there's a groundswell of support for a more modern API,
I'd be happy to work on it.

                                        Be seeing you,

Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

View raw message