dcsimg
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: Java
Expertise: Beginner
Sep 19, 1997

WEBINAR:

On-Demand

Building the Right Environment to Support AI, Machine Learning and Deep Learning


It's All a Matter of Trust

If you're building applets using Microsoft's Visual J++, you might encounter problems the first time you try to run your applet outside of the development environment. Typical examples of this are:
  • Your applet can't access local files (such as pictures required for animations) anymore;
  • Error messages about missing classes;
  • The annoying "Warning: Applet Window" message;
  • Other error messages that somehow seem to be security-related.
Puzzling though this may all seem, the reason is quite simple: all applets running inside the development environment are implicitly trusted, but once you run them outside VJ++, the Java VM will start to enforce security restrictions.

To make the Microsoft VM trust your applet (and thus make it run again), you'll have to create a Cabinet (.CAB) file for the applet and digitally sign that. The tools you need for this can be found in the 'Cab&Sign' directory on your VJ++ CD-ROM, although you'll also need a certificate from a commercial certification authority (like Verisign: see www.verisign.com for more information) if you plan to distribute your applets.

Michiel de
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date