AjaxProxy now longer needs servlet.jar

This was a major annoyance, as you just couldn't be sure where to put this frigging jar. In /Library/Java/Extensions? In /Library/WebObjects/Extensions? In a jar? In the app?

What about people (Oh, my! The poor, unfortunate creatures!) that need to deploy in a servlet container?

So the best thing is to avoid needing servlet.jar when you can. And that's what we did.

It's currently untested, so please report on the mailing list if things don't work.

But the only thing to watch out for is if you actually instatiate a JSONPRCBridge object yourself, which you normally wouldn't do if you use the AjaxProxy. If you do, then now use the JSONBridge and you're all set.