Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Loading java causes browser to hang, no console msg

 
Tom Corcoran
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have no problems running the app on my machine. The problem is when I deploy. I have 2 .jar files. When I try and load the first page of this swing app I get the Java sun logo in the browser.

v5.07 is installed and enabled in firefox/IE 6.

The html page which calls the applet uses referenced location for the jar files. I did also try adding the .jar file to a classpath vairable without any effect.

Right clicking the java icon in the tray and opening the console window, there is no entry after the home directory.

I can't think of what else to try. Any ideas?

Thanks a lot,

Tom.
 
Nathan Pruett
Bartender
Posts: 4121
IntelliJ IDE Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Lots of things could be causing this...

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.
 
Tom Corcoran
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic