Jukka Zitting wrote:
You're right. If the code is to remain in Apache Commons (i.e. not moved here to XML Commons), then we should probably rename it to something like Commons JAXP.
I for one am having increasing trouble sorting out just what's where and worked on by whom at Apache.
Looking at it as an interested outsider, I really think there should be one XML Project which includes Xerces, Xalan, and XML Commons. This proposal (which I still don't fully understand) belongs either in XML Commons or perhaps in a separate subproject called XML Utilities. The latter would make sense if the purpose of Commons is only to bundle common libraries like DOM and JAXP. However if that's the case then the resolver might need to move out of Commons into its own subproject. Xerces and Xalan should not be separate projects, or at least should be presented to the world that way. Right now the external organization at Apache seems to reflect the internal developer organization way too closely. It's time to decouple them.
But as I said, I don't really understand the logic (if any) of how it's organized now, so please clean it up however you can with an eye toward how this looks to outsiders.
It's possible that once this gets rolling I might be able to make some significant contributions of already written code, but as is I can't explain to my manager what it is you're doing and I'm not all that sure myself. I know my day job has some general purpose utility code for working with JAXP and SAX and what not that we've vaguely considered open sourcing one of these days, but whether it fits this project or not, I can't yet say.
-- Elliotte Rusty Harold [email protected] Refactoring HTML Just Published! http://www.amazon.com/exec/obidos/ISBN=0321503635/ref=nosim/cafeaulaitA --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
