I've been asked to create a one to two day Ajax course for Java developers. The problem is that I don't really know what is the best way to do this. I've created a 3 hour introduction where I show in detail how a simple application can be done quickly with DWR. It also shows a bunch of simple and advanced examples from all across the net, to whet peoples appetite for what can be done.
But what is the next step? Here's the options I've been pondering:
- Should I continue using DWR?
- Or should I show how to do Ajax with Struts, since that is most likely what the students are using now?
- Or should I show how to do Ajax with JSF, since that is most likely what the students will use in the future (bleech)?
- Or use Wicket, since that might be the most elegant way of doing it (just speculating here)?
- Or do it with ZK or Zimbra, since that might be the most powerful toolkits around?
Currently what I believe might be the best approach is to stick with DWR, mostly because I know it fairly well, it is simple, and can be used with any other web framework. I'd use DWR to implement some Ajax magic, then spend the rest of the time looking at Ajax patterns, i.e. how is Ajax typically used, and how is it typically implemented, from a 30,000 feet level.
Any kind of feedback would be most welcome!