Matt Raible has a post asking people for various statistics about their web framework of choice. He’s asking for numbers for the following:
How many tools (i.e. IDE plugins) are available for your web framework?
How many jobs are available for your framework on Dice.com? What about Indeed.com?
How many messages where [sic] posted to your user mailing [...]
Eelco took my original ten minute hack and ran with it, and has produced something that covers a lot more edge cases. It handles anonymous inner classes, externalizables, things with custom writeObject() functions and a bunch of other stuff. It also plays nicely with SecurityManagers. You can find the code in Wicket 1.3’s SerializableChecker.java. [...]
Ever had a java.io.NotSerializableException in your code and found it very hard to debug? The JVM stack trace is nearly useless, telling you which code triggered the serialization, but not what it is trying to serialize.
Particularly tedious are HTTP sessions that refuse to serialize. In Wicket we store detached components in the session between requests. [...]
I’ve found a mightily useful page explaining the world of Sun JVM options. Absolutely invaluable if you’re trying to squeeze everything out of your poor overloaded appserver.
The upcoming Wicket 1.3 and 2.0 versions intercept their requests using a servlet filter to provide more flexible resource mapping and nicer URLs. Your Wicket pages no longer need to live at foo.com/app/PageName and can instead be rooted properly at foo.com/PageName.
This is now working well. I did, however, come up against a small issue, which [...]