Sun Microsystems 2 manual Signature File Merge Rules, JSR 68-Based Merge

Page 25

Signature File Merge Rules

The -Filesargument of the SignatureTest command accepts values to specify one or more signature files that are combined to represent an API configuration that is used as input for testing. This resulting API-set can also be combined into a single signature file for testing purposes.

By default the API combination is assumed to be constructed according to the JSR 68 rules. This can be overridden during a SigTest tool test run by specifying the -NoMergeoption to run the signature test. The -NoMergeoption forces SigTest tool to use the first class description it encounters if more than one class with the same name is found in the set of signature files specified by the -Filesargument. In this case it uses the class from the left-most signature file that is specified with -Files.

JSR 68-Based Merge

The Java ME platform architecture specified by JSR 682 allows for the inclusion of several Java platform APIs in one conforming Java platform runtime environment. The condition for combining these APIs is that any application written for the resulting runtime environment must execute successfully on the combination.

If such a combination exists, it is defined on the basis of the combined sets of APIs with semantics, and the semantics must be compatible with those of all the included components.

The only means of verifying the semantics of the combination is to run the applicable test suite for each API. However, it is possible to automate the creation of a combined set of API signatures, and it is also possible to detect when a combined set cannot be built.

The Merge command functionality combines (merges) several input signature files into one resulting signature file, as follows: If A, B, and C are signature files, then A

+B yields signature file C, and each of the three signature files represent the corresponding classes of their respective APIs. The Merge process constructs the resulting API C out of the two input APIs A and B.

Merge Command Operative Principles

The Merge command operates according to the following principles, where A and B are input APIs that are combined into the resulting API C:

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

Chapter 2 Using the Signature Test Tool

11

Page 24 Page 26
Image 25
Page 24 Page 26
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 Before You Read This Guide Who Should Use This GuideHttp//jtharness.dev.java.net 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 Mode1Settings 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 Command Description Setup CommandJava com.sun.tdk.signaturetest.Setup arguments Help Debug Static Classpath pathNonClosedFile FileName filename ClosedFile File//pathPackage VerboseSignature File Formats Case Sensitivity of Command ArgumentsJava.lang.RuntimeException class, or 3Signature File Format CompatibilitySignature File Contents Signature File Body 4Signature File Content SummaryStrictfp Transient Volatile Synchroniz Native 5SignatureTest Command Arguments Help Debug Static Mode bin srcJava com.sun.tdk.signaturetest.SignatureTest arguments NoCheckValue CheckValueClassCacheSize sizeofcache 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 Code Example 2-1Unsorted Report Example Unsorted Report6SetupAndTest Command Argument Java com.sun.tdk.signaturetest.SetupAndTest argumentsHelp Reference path Java com.sun.tdk.signaturetest.Merge arguments Merge CommandHelp Files Write -Binary 7Merge Command ArgumentsQuick Start Examples Example Setup CommandJavac -d V1.0 V1.0/test.java Running the Setup CommandV1.0/example/test.class This completes the Setup command example Running SignatureTest Without the JavaTest Harness Example SignatureTest CommandJavac -d V2.0 V2.0/test.java STATUSFailed.3 errorsV2.0/example/test.class Running the SetupAndTest Command Example SetupAndTest CommandV2.0/example/test.class The API under test Setenv JRE Java-Home/jre/lib/rt.jarCode 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