我看到了RIA的希望，从服务端操纵JS说开去。

Posted by: Mileta Cekovic on December 02, 2005 in response to Message #192648 2 replies in this thread
This (JS widgets) library is the way to go for browser based applications. We need JS objects for widgets to be manipulated by client side JS code.

But, we also need these widget components on the server side too, preferably with the similar object model. With similar I meen that at least the names and meaning of the properties, methods and events are the same.

There are progreses on both sides (client and server) to provide decent component model, but we need unified one.

That means server side component framework which renders JS objects instead of HTML, letting JS objects render HTML. And the object model for both must be similar at least (as described above).


Yes, go for "server-side api" and "presentation engine"..
Posted by: Marc Domenig on December 02, 2005 in response to Message #192673 1 replies in this thread
I agree with Mileta. The "server-side" approach is preferable. Not only because of the object model api but also because it allows packing the shaky JS code into an application independent "presentation engine" such that you can write your apps in pure server-side Java.

This approach is feasible with JS, Java, or Flash, as described in http://www.javalobby.org/articles/ajax-ria-overview/.

You can find a concrete design solution in http://javadesktop.org/articles/canoo/index.html (based on Java, but also feasible in JS)

Posted by: Kito Mann on December 02, 2005 in response to Message #192693 1 replies in this thread
That's the benefit of JSF. A lot of JSF components are AJAX-enabled these days, and you still get a full component object model on the server. Otrix's WebStudio Enterprise, Oracle's ADF Faces, and JScape's WebGalielo components all include AJAX functionality (and will be including even more).
Kito D. Mann
Author, JSF in Action
http://www.jsfcentral.com
Posted by: Mileta Cekovic on December 02, 2005 in response to Message #192708 1 replies in this thread
But we need JSF renderers that render JS objects, NOT HTML. JS objects themselves should render HTML (and have 'the same' object model as JSF components if possible).