<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Code Java, deploy JavaScript/HTML with the Google Web Toolkit</title>
	<atom:link href="http://www.xlml.com/aehso/2006/05/18/code-java-deploy-javascripthtml-with-the-google-web-toolkit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.xlml.com/aehso/2006/05/18/code-java-deploy-javascripthtml-with-the-google-web-toolkit/</link>
	<description>John O'Shea's musings, observations and opinions on anything and everything.</description>
	<pubDate>Sat, 22 Nov 2008 01:41:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Aehso</title>
		<link>http://www.xlml.com/aehso/2006/05/18/code-java-deploy-javascripthtml-with-the-google-web-toolkit/#comment-1470</link>
		<dc:creator>Aehso</dc:creator>
		<pubDate>Wed, 24 May 2006 12:25:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.xlml.com/aehso/2006/05/18/code-java-deploy-javascripthtml-with-the-google-web-toolkit/#comment-1470</guid>
		<description>Yeah, I was going to post some examples of what the Java-&#62;Javascript compiler was producing...but...it was too big (and obfuscated) to make any sense on it's own!

The more I think about it, the more limited the use cases for this toolkit, even for Eclipse/Java developers.  A huge drawback is that the tolkit doesn't help with calling existing REST/SOAP interfaces from the generated clients - it's almost a walled garden (see http://web2.wsj2.com/googles_innovative_yet_limited_ajax_environment_gwt.htm)</description>
		<content:encoded><![CDATA[<p>Yeah, I was going to post some examples of what the Java-&gt;Javascript compiler was producing&#8230;but&#8230;it was too big (and obfuscated) to make any sense on it&#8217;s own!</p>
<p>The more I think about it, the more limited the use cases for this toolkit, even for Eclipse/Java developers.  A huge drawback is that the tolkit doesn&#8217;t help with calling existing REST/SOAP interfaces from the generated clients - it&#8217;s almost a walled garden (see <a href="http://web2.wsj2.com/googles_innovative_yet_limited_ajax_environment_gwt.htm" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/web2.wsj2.com');">http://web2.wsj2.com/googles_innovative_yet_limited_ajax_environment_gwt.htm</a>)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Mason</title>
		<link>http://www.xlml.com/aehso/2006/05/18/code-java-deploy-javascripthtml-with-the-google-web-toolkit/#comment-1075</link>
		<dc:creator>Justin Mason</dc:creator>
		<pubDate>Thu, 18 May 2006 12:15:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.xlml.com/aehso/2006/05/18/code-java-deploy-javascripthtml-with-the-google-web-toolkit/#comment-1075</guid>
		<description>'The generated Javascript code uses a Javascript-based JRE emulation library that provides “most of java.lang and a subset of java.util”.'

holy crap, that has got to craaaaaawl....</description>
		<content:encoded><![CDATA[<p>&#8216;The generated Javascript code uses a Javascript-based JRE emulation library that provides “most of java.lang and a subset of java.util”.&#8217;</p>
<p>holy crap, that has got to craaaaaawl&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
