, thanks for the tip re the HTTP server from the Apache XMLRPC project. It seems to only support serving XMLRPC content out-of-the-box, though, but maybe that could be overriden somewhere. I'll check into it. I prefer using a complete "package" as a base, rather than, for example, making my own classes from example code (hey, I'm pretty certain I could quite easily write my own simple HTTP 1.0 server if need be), because it's nice to have something that is maintained by a third party and can be upgraded by just exchanging a .jar file. For example, I use PircBot
for a small IRC bridge I've written, although writing an IRC client enough for my needs probably wouldn't have taken me more than a couple of hours (I've written several before). But this way, not only can I benefit from PircBot upgrades, but others using PircBot can also benefit from any potential bugs that I find and fix.
On quite another note, this is hilarious: Sex Scandal Rocks Wonka Factory.