"The Sun App server (Glassfish) really rocks. The thing is coming up in only 5 seconds together with derby and admin console. Compared to this most application servers should hide themselves ..."
That's really a huge step forward for J2EE - it should now be less painfull to always reboot the webserver after doing refactorings and program changes. ;)
I'm working with both: Java/J2EE and Smalltalk/Seaside and the situation is always the same:
I constantly see the Java world beeing happy about small things making this painfull style of development easier. Nobody asks the question if this change-compile-restart process makes sense in general!!!
On the other hand things like that have never been an issue in dynamic environments like Smalltalk. You dont have to restart the web server after large changes - even if you restructure large parts of your application framework or the web server code itself.
This is one factor why Smalltalk development makes you more productive - you can focus on solving the problem...