<link rel="stylesheet" type="text/css" href="../css/site.css"/> </head> <body> <table cellspacing="0" width="100%"> <tr height="90px"> <td> <a href="http://j2page.org"> <img border="0" src="../img/logo.png"/> </a> </td> <td id="navigation"/> <td rowspan="2" valign="top"> <script type="text/javascript">  </script> <script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js">  </script> </td> </tr> <tr> <td colspan="2" valign="top" style="padding-right: 5px;"> <table cellspacing="0" width="100%"> <tr> <td colspan="2" valign="top" style="padding-right: 5px;"> <h2>J2Page: Comparison With Other Java-to-JavaScript Converters</h2> <p>J2Page is certainly not the only tool that take the Java-to-JavaScript conversion route. This page lists other such tools of which we are aware:</p> <ul> <li> <p> <em>Google Web Toolkit</em> The most famous of these tools is undoubtably the <a href="http://code.google.com/webtoolkit/">Google Web Toolkit</a> (GWT for short). Read about the main differences between J2Page and GWT <a href="comparison-gwt.html">here</a>.</p> </li> <li> <p> <em>Java2Script</em> (aka J2S). From the project <a href="http://j2s.sourceforge.net/">site</a> "Java2Script (J2S) Pacemaker provides an Eclipse Java to JavaScript compiler plugin and an implementation of JavaScript version of Eclipse Standard Widget Toolkit (SWT) with other common utilities, such as java.lang.* and java.util.*. You can convert your SWT-base Rich Client Platform (RCP) into Rich Internet Application (RIA) by Java2Script Pacemaker." Thus the emphasis of J2S is to bring Eclipse's SWT to the web via JavaScript, which contrasts with the J2Page approach of simply "wrapping" existing JavaScript widget libraries. This difference has a few ramifications:</p> <ul> <li> <p>With J2S the standard API you are working with is Eclipe's SWT (Standard Widget Toolkit) while with J2Page the API is the browsers' standard DOM at the lowest level, or, at a higher level, your choice of existing JavaScript libraries.</p> </li> <li> <p>Applications written in J2S can be run both on the desktop (via SWT) or on the web. J2Page is intended to solely build web applications (although desktop-like functionality can be achieved via rich widget sets and offline storage).</p> </li> <li> <p>J2S handles the communication between browser and server under the hood in it's own fashion. With J2Page by contrast the developer controls the client-server communication and can choose the appropriate mechanism (DWR, JSON, SOAP, etc.)</p> </li> <li> <p>Despite these differences, there certainly is opportunities for code-sharing between the two projects, especially when it comes to building JavaScript equivalents to the Java standard libraries. We will be looking into such code sharing possibilities in the near-term future.</p> </li> </ul> </li> <li> <p>Do you know of any other tools that convert Java to JavaScript? Please let us know.</p> </li> </ul> </td> </tr> </table> </td> </tr> </table>  <script type="text/javascript"> var sc_project=2789452; var sc_invisible=0; var sc_partition=28; var sc_security="558f9528"; </script> <script type="text/javascript" src="http://www.statcounter.com/counter/counter_xhtml.js">  </script> <noscript> <div class="statcounter"> <a class="statcounter" href="http://www.statcounter.com/"> <img class="statcounter" src="http://c29.statcounter.com/2789452/0/558f9528/0/" alt="web metrics"/> </a> </div> </noscript>  </body> </html>