Sun Microsystems 2 Bootstrap and Extension Classes, Package PackageWithoutSubpackages Exclude

Page 24

CLASSPATH and -classpath Settings

TABLE 2-1lists the requirements for setting the CLASSPATH environment variable and the -classpathargument when running either the Setup or SignatureTest commands. The table uses the following terms to describe the classes that must be included:

■Required classes - All superclasses and superinterfaces of the classes under test

■Classes under test - The set of classes specified by a combination of the following options:

■-package

■-PackageWithoutSubpackages

■-exclude

TABLE 2-1Settings for the Setup and SignatureTest Commands

Variable or Argument

In Reflection Mode

In Static Mode

 

 

 

CLASSPATH environment variable

Must contain these:

•sigtestdev.jar or sigtest.jar.

•Classes under test.

•Other required classes, except for bootstrap and extension classes described in “Bootstrap and Extension Classes” on page 10.

Must contain either

sigtestdev.jar or sigtest.jar.

-classpath argument

Required. Must contain

Must contain these:

the classes under test.

• Classes under test.

 

• All required classes.

Bootstrap and Extension Classes

Bootstrap and extension classes are those located in rt.jar and several other JAR files under the Java-Home/jre/lib/directory, where Java-Homeis the base directory of the Java platform runtime installation. For example, classes from the java package such as java.lang.Object are bootstrap classes. Their location is already available to the Java Virtual Machine environment. Because of this, they do not need to be specified in the CLASSPATH environment variable when reflection mode is used. Furthermore, bootstrap and extension classes are always loaded from JAR files located in the Java-Home/jre/lib/directory, regardless of whether they were specified in the class path or not. This is an important feature of the reflection mode.

10 Signature Test Tool 2.0 User’s Guide • April 2008

Page 23 Page 25
Image 24
Page 23 Page 25
Contents SigTest Tool 2.0 User’s Guide Please Recycle Contents SignatureTest Command SetupAndTest CommandIndex Vi Signature Test Tool 2.0 User’s Guide April Tables Table A-1Viii Signature Test Tool 2.0 User’s Guide April Code Examples Signature Test Tool 2.0 User’s Guide April Who Should Use This Guide Before You Read This GuideHttp//jtharness.dev.java.net How This Guide Is Organized Related DocumentationTypographic Conventions Sun Welcomes Your CommentsXiv Signature Test Tool 2.0 User’s Guide April Introduction Signature Test BasicsWhat is Tested Mutual Binary Compatibility CheckMutual Source Compatibility Check Class and Class Member Attributes CheckedSource and Binary Compatibility Modes Using Custom Signature Loaders Signature Test Tool 2.0 User’s Guide April Using the Signature Test Tool Signature Test Tool BasicsReflection and Static Run Modes Generics Checking in Binary Mode Constant Checking in Differing Run ModesBootstrap and Extension Classes 1Settings for the Setup and SignatureTest CommandsPackage PackageWithoutSubpackages Exclude Merge Command Operative Principles Signature File Merge RulesJSR 68-Based Merge Element Handling by Merge Using the Signature Test Tool Setup Command Command DescriptionJava com.sun.tdk.signaturetest.Setup arguments Help Debug Static Classpath pathFileName filename ClosedFile File//path NonClosedFilePackage VerboseCase Sensitivity of Command Arguments Signature File FormatsJava.lang.RuntimeException class, or 3Signature File Format CompatibilitySignature File Contents 4Signature File Content Summary Signature File BodyStrictfp Transient Volatile Synchroniz Native Help Debug Static Mode bin src 5SignatureTest Command ArgumentsJava com.sun.tdk.signaturetest.SignatureTest arguments CheckValue NoCheckValueClassCacheSize sizeofcache Classpath see ClasspathErrorAll NoMergeFormatPlain Running a Signature Test With the JavaTest Harness SigTest-Directory/examples/sampleTCK/tck/tests/api/sigtestTestsuite-path/tests/api/signaturetest Report Formats Sorted ReportFileName ./name.sig Unsorted Report Code Example 2-1Unsorted Report ExampleJava com.sun.tdk.signaturetest.SetupAndTest arguments 6SetupAndTest Command ArgumentHelp Reference path Merge Command Java com.sun.tdk.signaturetest.Merge arguments7Merge Command Arguments Help Files Write -BinaryExample Setup Command Quick Start ExamplesRunning the Setup Command Javac -d V1.0 V1.0/test.javaV1.0/example/test.class This completes the Setup command example Example SignatureTest Command Running SignatureTest Without the JavaTest HarnessSTATUSFailed.3 errors Javac -d V2.0 V2.0/test.javaV2.0/example/test.class Example SetupAndTest Command Running the SetupAndTest CommandV2.0/example/test.class The API under test Setenv JRE Java-Home/jre/lib/rt.jarCode Example A-5SetupAndTest Command Output Example Merge Examples Running Merge ExamplesA.class Run command #2 Example Result Files Code Example A-7 Contents of ./x2.sig Code Example A-9 Contents of x1+x2.sig Signature Test Tool 2.0 User’s Guide April Sorted report, 24 static mode IndexUnsorted report
Related manuals
Manual 50 pages 18.14 Kb

2 specifications

Sun Microsystems, founded in 1982, was a significant player in the computing industry, best known for its innovative technology solutions and workstations, particularly the Sun-4, which represented a key milestone in the company's history. The Sun-4 architecture, launched in 1987, utilized the SPARC (Scalable Processor Architecture) RISC processor, notable for its high performance and scalability.

One of the primary features of Sun Microsystems' platforms was their ability to efficiently handle multitasking and resource management, making them ideal for enterprise-level applications and development environments. Sun-4 workstations boasted impressive graphics capabilities with the addition of advanced graphical user interfaces, support for color displays, and the SUNVIEW windowing system, which enhanced user experience and productivity.

The Sun-4 systems also supported the SunOS operating system, which was based on UNIX. This operating system was engineered for stability and robustness, offering features like multiuser support, networked environments, and advanced security options. Moreover, SunOS provided seamless integration with various programming languages, including C and C++, facilitating software development that aligned with industry standards.

Another standout characteristic of Sun Microsystems was its commitment to open systems and standards. By providing developers with comprehensive tools and environments, such as the Standardized Application Programming Interface (API) and support for networking protocols, Sun facilitated interoperability among different computing platforms. The emphasis on open architecture also meant that customers could easily upgrade their systems without being locked into proprietary solutions.

Sun Microsystems was also ahead of its time with innovations in network computing. Their workstations were among the first to support network file systems and distributed computing concepts, enabling seamless data sharing across multiple systems. With the introduction of the Network File System (NFS), Sun revolutionized how data was accessed and managed across networks, which played a significant role in the evolving landscape of client-server computing.

In summary, the Sun Microsystems 2 and its successive innovations in workstation technology highlighted the company's forward-thinking approach. By integrating powerful performance with open systems, robust operating systems, and advanced networking capabilities, Sun laid the groundwork for modern computing, influencing various sectors from academia to enterprise solutions. Even after its acquisition by Oracle in 2010, the legacy of Sun Microsystems continues to be felt across the computing industry.
Top Page Image Contents