We haven't felt the need to use GWT with Wicket. Wicket has handled all of our client side code very powerfully and efficiently- and we can do all development and debugging in standard Java IDE's which means there's none of the GWT object marshalling to write, debug and maintain.
What kind of client side stuff do you need GWT for that you can't do with Wicket alone? >-----Original Message----- >From: hariharansrc [mailto:[email protected]] >Sent: Saturday, 2 April 2011 4:17 PM >To: [email protected] >Subject: Re:thanks you all for giving proper suggestions > >i want to know whether i can use gwt along with wicket >so i can quite manage both server and client side coding efficiently >are there any tutorials to integrate gwt with wicket > >thank you in advance > >-- >View this message in context: http://apache- >wicket.1842946.n4.nabble.com/how-to-call-javascript-function-on-form- >submission-tp3408147p3421644.html >Sent from the Users forum mailing list archive at Nabble.com. > >--------------------------------------------------------------------- >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]
