Sun Microsystems 2 manual Using Custom Signature Loaders

Page 19

The use of building blocks created a need for more lenient checking of exception throw lists compared to earlier SigTest tool versions. Consequently, SigTest tool 1.5 provides both a source and a binary compatibility mode of operation. This retains compatibility with earlier signature files while adding support for building blocks and eliminating the unnecessary error messages.

The SignatureTest command recognizes the -modeoption that takes the values “src” or “bin” as arguments for choosing source mode or binary mode. The choice of which mode to use depends on the type of signature file being used in the test.

This is described in more detail later in these sections:

■“Setup Command” on page 14 describes how to generate a signature file

■“SignatureTest Command” on page 20 describes how to specify the mode when running a signature test

■“Merge Command” on page 27 describes how to generate a combined signature file from set of signature files

The difference between the binary and source compatibility modes is how the tool handles the throws list for constructors and methods (as described in “Class and Class Member Attributes Checked” on page 3). Constant checking behavior is also different in binary and source compatibility modes. Although constant checking can be applied to binary compatibility, it is a necessary prerequisite for source code compatibility. “Constant Checking in Differing Run Modes” on page 9 describes these differences in more detail.

Using Custom Signature Loaders

The signature test has a requirement for the Java™ Platform, Standard Edition (Java SE platform) runtime environment version 1.4 or later. This requirement might prevent use of the tool on limited or nonstandard environments such as some Java™ Platform, Micro Edition (Java ME platform) or Java™ Platform, Enterprise Edition (Java EE platform) configurations.

To overcome this, the tool provides support for custom signature loaders that can be implemented as plug-ins. These plug-ins gather signatures from a runtime environment when the SignatureTest command cannot be run directly. For example, you might create a light-weight remote JavaTest harness agent and run the signature loader on a remote Connected Device Configuration (CDC) compatible device. Another example is using a wrapped J2EE platform bean as a signature loader inside a J2EE platform container where any direct file I/O operations are prohibited.

Chapter 1 Introduction

5

Page 18 Page 20
Image 19
Page 18 Page 20
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 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 5SignatureTest Command Arguments Help Debug Static Mode bin srcJava com.sun.tdk.signaturetest.SignatureTest arguments Classpath see Classpath CheckValueNoCheckValue ClassCacheSize sizeofcacheNoMerge 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 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