This isn't a critical bug, of course: It's easy to work around (that is, replace) and frankly it's been an annoyance but not a real problem in my development efforts. Moreover, it seems like Sun has been pretty busy over the last few months working on other things. Nevertheless, this whole experience has frustrating.
First, in my limited and anecdotal experience the time to respond to bug reports is getting much worse. It took six months for the Java team to acknowledge this simple, and if I may say reasonably well documented (including a "patch" and unit test), bug.
Second, this is a good if trivial example of how Sun's community efforts fail in execution. Here's a trivially simple (it's clear from inspection alone) and readily demonstrated (a complete unit test is provided) defect. A trivially simple (one line, two if you add hashCode()) patch is provided, and yet it took six months to get the issue acknowledged. Now I'll wait an indeterminate amount of time to see the problem fixed. All that and this problem could have been analyzed, patched and regression tested in less time than it took me to write this post. Even the slowest moving of open source projects would have had this problem patched, if not released, in a matter of weeks. If Sun can't find a way to move more quickly (and stop chasing the most superficial features of C#) Java seems destined to be eclipsed by community developed languages.
I'll uncharacteristically paraphrase Jerry Seinfeld here: "Sun knows how to take community input, they just don't know what to do with it. And that's really the most important part of community: the doing." (text, audio)
PS: Also note that the second bug I linked to above, "Repackage sun.net.www.content.* Classes (java.net.ContentHandler)", was already addressed by the time I submitted it, I personally added a comment to this effect nearly two years ago, and yet the bug sits marked "In progress" (and with 3 votes, none of them mine).
Previous Topic
