Sun Microsystems 2 manual Signature File Body, 4Signature File Content Summary

Page 32

Signature File Body

The remaining body of a signature file immediately follows the header. It contains the following information, which is further clarified in TABLE 2-4:

For each public or protected class, all modifiers except strictfp, and the fully qualified name of any superclass or interfaces implemented, generic type parameters, and annotations.

For each public or protected interface, all modifiers except strictfp, and the fully qualified name of any superinterfaces implemented, generic type parameters, and annotations.

For each public or protected field, all modifiers except transient, the fully qualified name of the field’s type and its fully qualified name. If the field is a primitive or string constant, the value of the field is included.

For each public or protected method, all modifiers (except native, synchronized, and strictfp), the fully qualified name of the type of returned value, the method’s fully qualified name, types of all parameters, and the names of exceptions declared in a throws clause.

For each public or protected constructor, all modifiers, the fully qualified name of the constructor, types of all parameters, and any exceptions declared in a throws clause.

Note – All private types that are used in the definition of a public or protected item are substituted by their public or protected equivalent if possible, otherwise an error is generated. All types included in a signature file are either public or protected and not private or package local.

TABLE 2-4further summarizes the contents of a generated signature file. A plus (+) indicates a class modifier is included in a generated signature file and a minus (-) indicates it is ignored for that particular element. A blank cell indicates that the condition does not apply to a cell, for example, a class does not have a transient modifier so it is blank.

TABLE 2-4Signature File Content Summary

Modifier

Class or

Field

Method

Constructor

Nested Class

 

Interface

 

 

 

or Interface

 

 

 

 

 

 

public

+

+

+

+

+

 

 

 

 

 

 

protected

 

+

+

+

+

 

 

 

 

 

 

abstract

+

 

+

 

+

 

 

 

 

 

 

static

 

+

+

 

+

 

 

 

 

 

 

final

+

+

+

 

+

 

 

 

 

 

 

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

Image 32
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 Http//jtharness.dev.java.net Who Should Use This GuideBefore You Read This Guide 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 ModesPackage 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 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 Java com.sun.tdk.signaturetest.SignatureTest arguments Help Debug Static Mode bin src5SignatureTest Command Arguments CheckValue NoCheckValueClassCacheSize sizeofcache Classpath see ClasspathFormatPlain 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 Unsorted Report Code Example 2-1Unsorted Report ExampleHelp Reference path Java com.sun.tdk.signaturetest.SetupAndTest arguments6SetupAndTest Command Argument Merge Command Java com.sun.tdk.signaturetest.Merge arguments7Merge Command Arguments Help Files Write -BinaryExample Setup Command Quick Start ExamplesV1.0/example/test.class Running the Setup CommandJavac -d V1.0 V1.0/test.java This completes the Setup command example Example SignatureTest Command Running SignatureTest Without the JavaTest HarnessV2.0/example/test.class STATUSFailed.3 errorsJavac -d V2.0 V2.0/test.java 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.