Have you tried running through appletviewer first rather than running it in a webpage... appletviewer has a less strict sandbox than the browser, so it might show that your problems are related to that.
You say it causes the browser to "hang" - is the browser actully "hung" (like, you can't go to other webpages and have to kill the browser process to exit, etc.) or is your app not responding? If it's the second, there could be an exeption being thrown, but not being reported... are there any areas of the code with empty catch clauses? ie.
Errors won't be reported or dealt with at all in these cases, but the errors may cause the application to be unable to continue.
Write once, run anywhere, because there's nowhere to hide! - /. A.C.
Joined: Oct 11, 2006
Thanks for all the tips Nathan.
I figured it out eventually.
It tirned out to be because TableLayout.jar (layout manager used and distributed in the install) was readonly. Removing the readonly attribute solved the problem! Why would this need to be writeable?