Mike Cannon-Brookes wrote: > Ok - so if you're on this list you probably don't need convincing, but I > should post it anyway :) > > http://radio.weblogs.com/0107789/stories/2002/07/09/whyILikeWebwork.html
Good stuff! Really well written, and actually quite balanced :-) After a long break from the world of J2EE, I'm getting into the fray again, and yesterday had the pleasure of writing an RMI-stack on top of WebWork (using the ClientDispatcher as transport), since we need to be able to call the server from an applet through firewalls. The whole thing was written in 2 hours, and was made out of three classes: 1) a RemoteServiceFactory that uses the Proxy API to create remote proxies (of ANY interface, that does not need to extend Remote or use RemoteExceptions). 2) Proxy InvocationHandler to handle calls on the client which delegates to 3) a RemoteAction that carries the invocation through the ClientDispatcher, executes it on the server, and then carries the result back up through 2) That was that. I'm sure it will be extended in the future, but this alone allowed remote calls from an applet into the server. Pretty neat. And since webworkclient.jar is only 14k it's pretty small too. I'll probably be extending the ClientDispatcher stuff rather soon, since for our project we need semi-asynchronous events back to the applet while a call is being executed (for progress bars and such). Since all communication is done through the CD this becomes trivial to implement :-) Me like it. /Rickard ps. and instead of EJB we're using AOP which makes the app really ultracool, but that's another story.. -- Rickard Öberg ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf _______________________________________________ Webwork-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webwork-user
