Bad Java…

I wonder why Java libraries are often of such an execrable quality? I have been working professionally with Java for about half a decade now, and truly, most Visual Basic OCX’s are better…

The standard class libraries that come with your average jdk are not content to address a wide range of functionality, but do so using a wide range of constructions, conventions and designs. Compared to the Classpath boys Sisyphus had it easy.

And then there are the third party abominations, of which Project JXTA surely is the premier contender for tar and feathers. With every new release the library is tailor made for yet another pet project of its developers. I have had the personal misfortune of having had to maintain a product based on JXTA, and I’m exceedingly happy to say that I have been able to convince my powers-that-be that we had better drop the effort to port the JXTA 1 based application to JXTA 2.

Only… Now I’m trying to get a reliable communication going between Jakarta HttpClient and Jetty. It may sound unbelievable, but trying to use the client to post a http port request to a servlet in jetty leads regularly to broken pipes, read errors, spurious end-of-files and what-not on either side. On the same machine — without even actually going through a network.

Come on! Even the six-year old http server an ex-colleague of mine had coded up as a quick hack in the last half hour before going home of an evening was more stable than this mainstay of the enterprise-ready JBoss application server.