Am 29.02.16 um 23:10 schrieb Robert Hanson:
> I believe that is the correct behavior. It's just that in the case of
> the JavaScript version of the applet you get an HTML error message, and
> in Java you get a Java error message. Your code is just printing that
> error message (fileData).
>
> But I see. you were expecting load("xxxx") to throw an error instead.
> That does make sense to me. But, if you think about it, there's no way
> for the applet to know what the HTML will be that defines a "file not
> found" error. These messages vary a lot. It is tested when you actually
> /load /the file, because we know in that case what the options are, and
> those error messages are not of them.
>
> But with load("xxxx") the file to load could be anything, including a
> file that reports exactly that HTML. So it never throws an error, and
> you just have to check to make sure yourself that you have the data you
> expect.
>
I am confused.
Isn't a Java exception exactly what a 'try / catch' is intended for?
And in the case of a http request : couldn't Jmol use the http response
code (e.g.: 200 => ok, 404 => file not found) to recognize errors?
Regards,
Rolf
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
