>>> Tapestry And GWT (Google Web Toolkit) >>> >> >> Tapestry and GWT may be compared but it's a kind of different breed. >> Integrating GWT in Tapestry works well and is a kind of quick use. >> >Well, so it worths to say that, explaining why they are different breed, and >that they may work together.
All of the stuff you can read on the GWT site they say about GWT vs. Web App Frameworks should be apply also to GWT vs. Tapestry. To get you started: GWT and Tapestry have in common: Both are Web Techs, Both have a client and server side, GWT vs. Tapestry: * GWT does not claim nor wants to be a full WebApp multipage framework but a WebApp singlepage framework (GWT Apps lose state when page refreshes or changes - beside using gears) * GWT is mostly about describing JavaScript using Java whereas Tapestry is about describing HTML using Java and Templates. * GWT is all about AJAX (yes I know there are certain areas where no AJAX is used at all for instance the view of client side information stores) and Tapestry is about HTML with some AJAX if you like to. -> Tapestry uses plain 'old' HTML Requests with some XHR where as GWT talks only XHR (untrue if you are geek and use GWT to extrem of cause :-)). * GWT uses a single servlet endpoint serving AJAX remote calls (XML, JSON) and Tapestry has multi-pages with IOC (SOA) and can perform all three kinds of AJAX requests (JSON, XML, HTML). * GWT can be embedded within Tapestry pages but a Tapestry page can not be embedded within GWT pages (beside IFrames). You will need your own JavaScript to let a tapestry page talking to GWT and vise versa. Best would be a matrix with all those features supported and unsupported or the need of extension. For example writing Multipage applications easily (supported by wicket and tap but not by GWT). Providing IOC (Supported Tap, Wicket with extension (as far as I know) and not supported by GWT. Dependency Injection (Tap, Wicket but not GWT) and so on. Some of these statements are questionable and describe the best practice uses and recommondations of the creator of the frameworks. For instance you can crack up Tapestry to provide services for a GWT Application and deliver HTML you can parse with your GWT pages and include it using setInnerHtml for instance but this use is discorraged and can lead you on a troubling road. -- Francois Armand Etudes & Développements J2EE Groupe Linagora - http://www.linagora.com Tél.: +33 (0)1 58 18 68 28 ----------- InterLDAP - http://interldap.org FederID - http://www.federid.org/ Open Source identities management and federation --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
