Why J2Page?
There are many tools available for developing web-based user interfaces using Java (some might say too many...),
so why would anyone want to use J2Page, and how does it compare to existing options? In a nutshell:
-
Most Java web frameworks require a server-side runtime component. With J2Page it is
possible to build your interface solely on the client side, calling back to a web service or some other RPC
mechanism to interact with the server as needed. In other words, developers can build pure Ajax solutions
by writing their code in Java instead of JavaScript.
-
Other frameworks that take a similar Java-to-JavaScript approach have proprietary APIs and
class libraries. J2Page relies solely on the W3C standard DOM (Document Object Model). Rather than introduce its own
proprietary API, J2Page is designed to take advantage of the numerous high-quality JavaScript Ajax libraries that
are now appearing such as Dojo, OpenRico, YUI, etc.
For a more in-depth comparison on how J2Page fits in with other popular web development technologies, please
see the following:
|