Sun Microsystems 2 Constant Checking in Differing Run Modes, Generics Checking in Binary Mode

Page 23

Note – In static mode you can test specified classes in another runtime environment. For example, this can be useful to analyze APIs that are part of a Java SE platform

1.4.2environment when the SignatureTest command is run on a Java SE platform version 5.0.

Constant Checking in Differing Run Modes

The requirements related to constant checking differ in binary and source compatibility testing. Although constant checking can be applied to binary compatibility, it is a necessary prerequisite for source code compatibility. Use the -staticmode to enforce strict constant checking in source code compatibility testing.

When running a signature test in source compatibility mode and using the static mode, constant checking is strict and two way. This means that all the constant fields and their related values specified in the reference API must have the same values in the API under test. Likewise, all the constant fields and their related values specified in the API under test must have the same values in the reference API.

In binary compatibility mode, the requirements related to constant checking are less strict. The signature test verifies that all the constant fields and associated values contained in the reference API are also available in the API under test. If any field values are missing or different, it reports an error. However, the signature test does not report an error if constant values are found in the API under test that are not available in the reference API.

Generics Checking in Binary Mode

The information related to generics is not used by the Java Virtual Machine1 at runtime. This information is used only by the compiler at compile time.

In binary mode the SignatureTest command compares the signatures of parameterized types after omitting the type parameters and arguments from both the signature file and the analyzed API (termed type erasure). This is to ensure that they are compatible at runtime. See The Java Language Specification, Third Edition, for a detailed description of type erasure.

The bridge methods that are generated by the compiler during type erasure are not a part of the API and so they are ignored by the SigTest tool.

1. The terms "Java Virtual Machine" and "JVM" mean a Virtual Machine for the Java™ platform

Chapter 2 Using the Signature Test Tool

9

Page 22 Page 24
Image 23
Page 22 Page 24
Contents SigTest Tool 2.0 User’s Guide Please Recycle Contents SetupAndTest Command SignatureTest CommandIndex Vi Signature Test Tool 2.0 User’s Guide April Table A-1 TablesViii Signature Test Tool 2.0 User’s Guide April Code Examples Signature Test Tool 2.0 User’s Guide April Http//jtharness.dev.java.net Who Should Use This GuideBefore You Read This Guide Related Documentation How This Guide Is OrganizedSun Welcomes Your Comments Typographic ConventionsXiv Signature Test Tool 2.0 User’s Guide April Signature Test Basics IntroductionMutual Binary Compatibility Check What is TestedClass and Class Member Attributes Checked Mutual Source Compatibility CheckSource and Binary Compatibility Modes Using Custom Signature Loaders Signature Test Tool 2.0 User’s Guide April Signature Test Tool Basics Using the Signature Test ToolReflection and Static Run Modes Constant Checking in Differing Run Modes Generics Checking in Binary ModePackage PackageWithoutSubpackages Exclude Bootstrap and Extension Classes1Settings for the Setup and SignatureTest Commands JSR 68-Based Merge Merge Command Operative PrinciplesSignature File Merge Rules Element Handling by Merge Using the Signature Test Tool Help Debug Static Classpath path Setup CommandCommand Description Java com.sun.tdk.signaturetest.Setup argumentsVerbose FileName filename ClosedFile File//pathNonClosedFile Package3Signature File Format Compatibility Case Sensitivity of Command ArgumentsSignature File Formats Java.lang.RuntimeException class, orSignature File Contents Signature File Body 4Signature File Content SummaryStrictfp Transient Volatile Synchroniz Native Java com.sun.tdk.signaturetest.SignatureTest arguments Help Debug Static Mode bin src5SignatureTest Command Arguments Classpath see Classpath CheckValueNoCheckValue ClassCacheSize sizeofcacheFormatPlain ErrorAllNoMerge Testsuite-path/tests/api/signaturetest Running a Signature Test With the JavaTest HarnessSigTest-Directory/examples/sampleTCK/tck/tests/api/sigtest FileName ./name.sig Report FormatsSorted Report Code Example 2-1Unsorted Report Example Unsorted ReportHelp Reference path Java com.sun.tdk.signaturetest.SetupAndTest arguments6SetupAndTest Command Argument Java com.sun.tdk.signaturetest.Merge arguments Merge CommandHelp Files Write -Binary 7Merge Command ArgumentsQuick Start Examples Example Setup CommandV1.0/example/test.class Running the Setup CommandJavac -d V1.0 V1.0/test.java This completes the Setup command example Running SignatureTest Without the JavaTest Harness Example SignatureTest CommandV2.0/example/test.class STATUSFailed.3 errorsJavac -d V2.0 V2.0/test.java Setenv JRE Java-Home/jre/lib/rt.jar Example SetupAndTest CommandRunning the SetupAndTest Command V2.0/example/test.class The API under testCode Example A-5SetupAndTest Command Output Example Running Merge Examples 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 Index Sorted report, 24 static modeUnsorted 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