>. Zope and Plone are quite well known, but holy learning curve.
I know this is off topic but one thing I don't get is why people always say the Zope has a huge learning curve. I have never seen a framework that didn't have a learning curve, but comparing zope to J2EE (oh an whatever App server you also need to run your J2EE solution) is being way to unfair on zope. (Have you ever had to set up a tomcat/apache/J2EE/oracle environment, just so you can do some basic persistent web app ;-)
With zope you can be very productive very quickly. The more you use it the more you learn and the greater the sophistication of what you can then do. But you don't have to get into the bowels from day one.
Maybe it's the lack of docs. Last time I looked at least. And the near-requirement to setup Squid for any reasonable speed. The big long paper the Quixote guys at MEMS wrote (about why they developed Quixote rather than using Zope) addresses it far better than I ever could.
And getting a java servlet container up and running these days isn't so bad at all. Dropping jar's in is nice too.