There are also some JAR Manifest changes in 7u45, as detailed at 
http://www.oracle.com/technetwork/java/javase/7u45-relnotes-2016950.html#newft

I don't know if that can explain the complete failure to load and the 
InvocationTargetException, or is just an additional issue.  

-----Original Message-----
From: Mickey Segal [mailto:[email protected]] 
Sent: Friday, October 18, 2013 6:37 AM

We were able to get past the problem of getCodeBase() returning null by 
hard-coding the URL.  This worked in 7 update 25 and 7 update 40.  We were able 
to debug that problem because the applet would launch and we could use println 
statements find that the problem was getCodeBase() returning null.  But the 
problem with 7 update 45 is that we don't even get to the stage of anything 
appearing in the Java Console; even from a println at the beginning of the 
code.  So we don't have a set of stacked Exceptions because the only clue that 
InvocationTargetException is involved is an error dialog that come up, but when 
one clicks the option for details, the Java Console is displayed, but no 
messages appear. 


Reply via email to