all items
rss feed

/ \
Ugh, stop twitching
banned from the end of the world
coding Posted 2008-08-02 02:49:46 by Jim Crawford
So I've pulled the rug out from another project of mine in favor of the new hotness, a potentially exciting web project based around Google Web Toolkit, which is essentially a Java to Javascript compiler plus a minimal AJAX library.

GWT is interesting and potentially useful, but it seems really raw and beta even at version 1.4. For instance, if you try to build a project with malformed XML in the configuration file, you get a stack trace rather than an error message. For another, there's this little joy of an alert that I get when trying to run a simple RPC test from GWT In Practice:

There was an error:
<html> <head> <script language='javascript' src='com.helloserver.HelloServer.nocache.js'> </script> </head> <body> <iframe src="javascript:''" id='__gwt_historyFrame' style='width:0;height:0;border:0'> </iframe> </body> </html>
That's what I get, I get an exception identifier and a content-free snippet of HTML. No stack trace. No additional information in the server window, no information in the console I ran the whole shebang from. No logs anywhere, as far as I can tell. No mention of anything like this in the troubleshooting section of the book the example is from. Google searches for that exception identifier are largely fruitless. I could break out the big hammer at this point and start tracing through the machine-generated Javascript in FireBug, but give me a fucking break.

So I post the problem to the GWT Google Group, leaving out the parts about how GWT seems really raw and beta and how they should give me a fucking break. I subscribe to the group and get a couple digests that don't contain the answer to my question.

I stop getting digests after 10am today, go back to the group page to see what's up, and it turns out I'm banned. Not clear why, no recourse to contact the administrator to find out. Since I'm banned, I can't even look at my post to see if I was inadvertently rude somewhere, though it wouldn't surprise me if the post vanished as part of the ban.

I'd love to start throwing out conspiracy theories, but my guess is actually that the admin saw the <script> element in the error message I posted and assumed I was trying to post an XSS exploit or something.
[link to this] [See more on “coding”]

the answer
Posted by Jim Crawford on 2008-08-04 00:35:29
In case you got here googling this particular problem, I got some help on this over at the GWT in Practice publisher's forum.

And also, seemingly coincidentally, some help from the same guy -- one of the authors of GWT in Practice, I now notice -- over at this post's mirror on my Livejournal.
add a comment
Only anonymous comments are available for now until I get the user system up and running again. Not many people were logging in anyway, so enh.
Permitted HTML tags: <b>, <i>, <u>, <tt>. Also permitted is the <q> pseudo-tag which is meant to delimit quotes from other messages.
To prove you are sentient, please type "sentient" into this box

what's this?
This is Jim Crawford's blog. Details and contact information.

On Twitter: @mogwai_poet

recent comments
no subject (Anonymous on we give you the numbers. use the numbers!)
no subject (Anonymous on #weightedsixes
: back and with more bots than ever)
no subject (Anonymous on i didn't say it, he said it)
no subject (Anonymous on digital: a love story -- one-hour review)
no subject (Anonymous on clipping a line segment to a triangle)
no subject (Anonymous on dance dance revolution in the future)
no subject (Anonymous on the best way to eat beans)
no subject (Anonymous on gta3 for gba: the burning question)
no subject (Anonymous on duke nukem forever -- one-hour review)
no subject (Anonymous on take a key for coming in)
no subject (Anonymous on super monkey ball 2 mini-review)
no subject (Anonymous on bioshock, system shock 2, and fear)
no subject (Anonymous on tim's working on physics)
no subject (Anonymous on a review of actionbutton.n
no subject (Anonymous on experts; atari 2600 display hardware)
Comments RSS