Sun Microsystems 2 manual Reflection and Static Run Modes

Page 22

■Merge - Creates a combined signature file from several signature files representing different Java APIs in one Java runtime environment according to the JSR 68 rules.

The SigTest tool distribution includes a Java™ Archive (JAR) file used for developing a signature test and one for distribution within a finished test suite to run its signature test. The description of each follows:

■sigtestdev.jar - Contains classes for running the commands used during signature test development.

■sigtest.jar - Contains only the classes for running the SignatureTest command. This file is distributed in a finished test suite.

Test suite developers perform these operations while using sigtestdev.jar to develop a signature test.

1.Run the Setup command to create a signature file from either an API defined by a specification or a reference API implementation.

2.Include the files required to run the signature test in the finished test suite distribution.

Testers perform these operations using sigtest.jar while testing the implementation, as described in “Running a Signature Test With the JavaTest Harness” on page 23.

1.Run the SignatureTest command to compare the reference representation of the API in the signature file to the API under test and produce a report. This step is usually performed under the control of the JavaTest harness as described in “Running a Signature Test With the JavaTest Harness” on page 23.

2.Interpret the report.

Reflection and Static Run Modes

Two run modes are available during command execution. These modes determine how the class descriptions are examined and retrieved, as follows:

■Reflection Mode - Uses reflection to examine API classes and retrieve information about them. The reflection mode is of greatest advantage when the API to be analyzed has no external class files.

■Static Mode - Specified with the -staticflag, the tool parses only the class files listed in the -classpathcommand-line argument.

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

Page 21 Page 23
Image 22
Page 21 Page 23
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 Before You Read This Guide Who Should Use 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 Modes1Settings for the Setup and SignatureTest Commands Bootstrap and Extension ClassesPackage PackageWithoutSubpackages Exclude Signature File Merge Rules Merge Command Operative PrinciplesJSR 68-Based Merge Element Handling by Merge Using the Signature Test Tool Java com.sun.tdk.signaturetest.Setup arguments Setup CommandCommand Description Help Debug Static Classpath pathPackage FileName filename ClosedFile File//pathNonClosedFile VerboseJava.lang.RuntimeException class, or Case Sensitivity of Command ArgumentsSignature File Formats 3Signature File Format CompatibilitySignature File Contents 4Signature File Content Summary Signature File BodyStrictfp Transient Volatile Synchroniz Native 5SignatureTest Command Arguments Help Debug Static Mode bin srcJava com.sun.tdk.signaturetest.SignatureTest arguments ClassCacheSize sizeofcache CheckValueNoCheckValue Classpath see ClasspathNoMerge ErrorAllFormatPlain SigTest-Directory/examples/sampleTCK/tck/tests/api/sigtest Running a Signature Test With the JavaTest HarnessTestsuite-path/tests/api/signaturetest Sorted Report Report FormatsFileName ./name.sig Unsorted Report Code Example 2-1Unsorted Report Example6SetupAndTest Command Argument Java com.sun.tdk.signaturetest.SetupAndTest argumentsHelp Reference path Merge Command Java com.sun.tdk.signaturetest.Merge arguments7Merge Command Arguments Help Files Write -BinaryExample Setup Command Quick Start ExamplesJavac -d V1.0 V1.0/test.java Running the Setup CommandV1.0/example/test.class This completes the Setup command example Example SignatureTest Command Running SignatureTest Without the JavaTest HarnessJavac -d V2.0 V2.0/test.java STATUSFailed.3 errorsV2.0/example/test.class V2.0/example/test.class The API under test Example SetupAndTest CommandRunning the SetupAndTest Command 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