Sun Microsystems 2 manual Source and Binary Compatibility Modes

Page 18

■In source mode only, the normalized list of thrown exceptions, described earlier, where order is insignificant

■Fields:

■Set of modifiers, except transient

■Field type

■Documented annotations with SOURCE and RUNTIME retention of the following types:

■Classes and interfaces

■Fields, methods and constructors

■Parameters and annotation types

The tool performs the check in the following order:

1.For all top-level public and protected classes and interfaces, it compares the attributes of any classes and interfaces with the same fully qualified name.

2.Taking into account all declared and inherited members, it compares all public and protected members of the same kind and same simple name, treating constructors as class members for convenience sake.

Source and Binary Compatibility Modes

Earlier SigTest tool versions performed a comparison of all exceptions declared in throws clauses for methods and constructors. Certain variations in this area caused an error message during the signature test. Despite these error messages, the source files compiled successfully together. Successful compilation is the basic criteria for source compatibility with the the current SigTest tool, while successful linking as the basic criteria for binary compatibility.

Changes to the throws clause of methods or constructors do not break compatibility with existing binaries because these clauses are checked only at compile time, causing no linkage error. For the purpose of signature testing, this relates directly to binary compatibility as described earlier in “Mutual Binary Compatibility Check” on page 2.

The adaptation of JSR 68, The Java™ ME Platform Specification, formalized the use of building blocks in API development. A building block is a subset of an existing API that is approved for reuse in the construction of profiles or optional packages. The building block concept enables a developer to duplicate the functionality provided by another API without having to redefine an entirely new API. For further details see JSR 68 at

http://www.jcp.org/en/jsr/detail?id=68.

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

Page 17 Page 19
Image 18
Page 17 Page 19
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 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 Help Debug Static Mode bin src 5SignatureTest Command ArgumentsJava com.sun.tdk.signaturetest.SignatureTest arguments ClassCacheSize sizeofcache CheckValueNoCheckValue 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 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