org.eclipse.platform.doc.isv/porting/3.3/faq.html

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.4 - (download) (as text) (annotate)
Tue Mar 24 14:00:00 2009 UTC (8 months ago) by mcq
Branch: MAIN
CVS Tags: v20090922-0800, v20091103-0800, r351_v20090821-0800, v20090908-0800, v20090811-0800, v20091013-0800, v20090528-2000, v20090513-2000, v20090714-0800, v20090825-0800, v20090902, v20090611, v20090526-2000, v20090601-2000, v20090727, v20090504-2000, v20090601-1909, v20090505-2000, v20091020-0800, v20090421-0800, v20090414-0800, v20090429-1800b, v20090527-2000, v20090728-0800, v20091124-0800b, R3_5, v20090707-0800, v20090429, v20090425, v20090506-2000, v20090331-0800, v20090507-2000, v20090915, v20091026-1200, r351_v20090810-0600, v20090902-1317, v20091117-0800, v20090602, v20090603, v20090522-1100, v20090604-2000, r351_v20090708-0800, v20090508-2000, v20090602-2000, v20090531-2000, v20090810, v20090527-2010, v20090506_1800, v20090521-2000, v20090929-0800, v20090921-1800, v20090427-1800, v20090407-0800, v20090426-2000, v20090603-2000, v20090413, v20091110-0800, v20090914-0800, v20090730-2000, v20090514-2000, v20090520-2000, v20090901-0800, v20090818-0800, r351_v20090831, R3_5_1, v20090604, v20090511-2000, v20091006-0800, v20090429_1800, v20090803-1800, HEAD
Branch point for: R3_5_maintenance
Changes since 1.3: +1 -1 lines 
Added lang="en" to html, and xml:lang="en" to xhtml files.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en">
<head>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
<title>Eclipse 3.3 Plug-in Migration FAQ</title>
</head>

<body>

<h1>Eclipse 3.3 Plug-in Migration FAQ</h1>
<ol>
	<li><a href="#signing">Impact of JAR signing</a></li>
</ol>
<h2><a name="signing">Impact of JAR signing</a></h2>
<p>
In Eclipse 3.3, plug-ins in the Eclipse platform are signed with a cryptographic
signature supplied by the Eclipse Foundation. Signing of plug-ins can have an impact
in three areas:</p>
  <ul>
    <li>Code that uses non-Eclipse class loaders.  Eclipse class loaders have a flag
    that controls load-time verification of signature, and it is turned off by default.  Loaders in
    the JDK such as URLClassLoader do not have this option, and will always verify
    any JAR file that contains signatures.  If this performance impact is not acceptable,
    the only solution is to avoid signing of JARs that are loaded by other class loaders.
    A common example is JARs that are intended to be run with Ant. </li>
    <li> Use of the constructor <tt>java.util.jar.JarFile(File)</tt> (i.e., without verify = false). 
    JarFile will perform verification of signatures unless explicitly told not to. This will
    have a performance impact when the JAR is signed. If you don't need signature verification,
    be sure to use the <tt>JarFile</tt> API that does not perform verification.</li>
    <li>Use of <tt>java.util.jar.Manifest</tt>.  Since the manifest file of a signed JAR can
    be quite large, anyone reading and parsing entire manifest.mf files will see a
    performance hit. The best solution in this case is to only read the manifest
    main attribute rather than parsing the entire file.</li>
  </ul>


</body>
</html>