Hello! We are currently happily using Wicket to develop our web applications. Wicket rules!
However, now we are required to make "embeddable Ajax components", you know, like Google Maps that anybody can embed in their own html. Can anybody suggest an approach that would allow us to keep as much overlap/reusability/cohabitation between our existing Wicket apps and these Ajax components that we now need to make? For instance, would a reasonable approach be to use only Sciptaclous components in Wicket so we can use the exact same lib for our embeddable components? I guess ideally I'd like to be able to serve the XHRs from these components directly from Wicket (ultimate reusability/cohabitation), but this doesn't look like it would be an easy task... Any comments would be most welcome. I'm new to this. :-) Cheers, Dave ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
