Re: [Webwork-user] Why I like WebWork

[Rickard <ri...@dr...>]

Mike Cannon-Brookes wrote:
> Ok - so if you're on this list you probably don't need convincing, but =
I
> should post it anyway :)
>=20
> http://radio.weblogs.com/0107789/stories/2002/07/09/whyILikeWebwork.htm=
l

Good stuff! Really well written, and actually quite balanced :-)

After a long break from the world of J2EE, I'm getting into the fray=20
again, and yesterday had the pleasure of writing an RMI-stack on top of=20
WebWork (using the ClientDispatcher as transport), since we need to be=20
able to call the server from an applet through firewalls. The whole=20
thing was written in 2 hours, and was made out of three classes:
1) a RemoteServiceFactory that uses the Proxy API to create remote=20
proxies (of ANY interface, that does not need to extend Remote or use=20
RemoteExceptions).
2) Proxy InvocationHandler to handle calls on the client which delegates =
to
3) a RemoteAction that carries the invocation through the=20
ClientDispatcher, executes it on the server, and then carries the result=20
back up through 2)

That was that. I'm sure it will be extended in the future, but this=20
alone allowed remote calls from an applet into the server. Pretty neat.=20
And since webworkclient.jar is only 14k it's pretty small too.

I'll probably be extending the ClientDispatcher stuff rather soon, since=20
for our project we need semi-asynchronous events back to the applet=20
while a call is being executed (for progress bars and such). Since all=20
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=20
ultracool, but that's another story..

--=20
Rickard =D6berg