Menu ▾ ▴

#18 Quiet failure with missing jar

open
Peter Smith
None
5
2011-02-27
2011-02-25
Anonymous
No

Peter,

I'm new to WinRun4J but so far, it looks like the best of the launchers I've tried. Good job.

While testing possible end user errors, I removed the jar with the main class just to see what would happen. My users will not be using a console. Typical is double click or launch from the Start menu. The JVM fails because it can't find the main class and WinRun4J prints the stack trace in the log. There is no popup for the user, just the splash screen flashing briefly.

I read through the code and it looks like you tried to use a popup for fatal errors that occur before the app's Java code has control (at which time the app can deal with the user). This case seems to slip by because although the app's Java code has "started", it never gets control.

Am I correct in assuming the intent is that the user always gets something, either from WinRun4J or from the app?

I realize that this situation could be prevented with an embedded jar, but the "Beta Quality" attribute means I don't want to give it to my users. (I will try testing it though)

Thanks for the code

Charlie

Discussion

  • Peter Smith

    Peter Smith - 2011-02-27

    Thanks for the feedback, much appreciated.

    The intention of the error popup was to provide information to the user in cases that were out of the control of the developer. The assumption was that if the jars were in the right place this wouldn't be a problem.

    But, I agree, it seems reasonable to add a popup here. I'll add this to my todo list.

    Thanks.

     

  • Peter Smith

    Peter Smith - 2011-02-27
    • assigned_to: nobody --> poida_smith