The fact that we don't have javascript support etc. build in yet, doesn't mean it is not useable. You can do Javascript, AJAX, whatever right now if you want to. It's just not yet totally integrated, which actually only means that you'll not be able to create high level reuseable components with JS/ AJAX/ etc.
I also think the clustering options are suited for production now. Might need a few tweaks here and there, but it's allready so much better than the Struts-like frameworks we're used to. And if you want to develop client-state pages, you can do that now (using bookmarkable pages). It's just that we're gonna make it even easier in 1.1.
Eelco
if it helps any, i believe this is not going to be any /long term/ trouble. right now, i would not base a million dollar large-scale web app on wicket...
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
