Java™ Platform Overview
The JRE provides the libraries, Java virtual machine, and other components necessary for you to run applets and applications written in the Java programming language. This runtime environment can be redistributed with applications to make them free-standing.
Java SE Development Kit (JDK)
The JDK includes the JRE plus command-line development tools such as compilers and debuggers that are necessary or useful for developing applets and applications.
Java Programming Language
The Java Programming Language is a general-purpose, concurrent, strongly typed, class-based object-oriented language. It is normally compiled to the bytecode instruction set and binary format defined in the Java Virtual Machine Specification. For more information see Language Features.
Java Virtual Machines
The Java virtual machine is an abstract computing machine that has an instruction set and manipulates memory at run time. The Java virtual machine is ported to different platforms to provide hardware- and operating system-independence.
The Java Platform, Standard Edition provides two implementations of the Java virtual machine (VM):
Java HotSpot Client VM
The client VM is an implementation for platforms typically used for client applications. The client VM is tuned for reducing start-up time and memory footprint. It can be invoked by using the -client command-line option when launching an application.
Java HotSpot Server VM
The server VM is an implementation designed for maximum program execution speed, trading off launch time and memory. It can be invoked by using the -server command-line option when launching an application.
For more information, see the VM documentation.
Base Libraries
Classes and interfaces that provide basic features and fundamental functionality for the Java platform.
Lang and Util Packages
Provides the fundamental Object and Class classes, wrapper classes for primitive types, a basic math class, and more. See the Lang and Util documentation for more information.
Math functionality includes floating point libraries and arbitrary-precision math. For more information, see the Math documentation.
Monitoring and Management
Comprehensive monitoring and management support for Java platform including Monitoring and Management API for Java virtual machine, Monitoring and Management API for the Logging Facility, jconsole and other monitoring utilities, out-of-the-box monitoring and management, Java Management Extensions (JMX), and Oracle’s Platform Extension. See the Monitoring and Management documentation for more information.
Package Version Identification
The package versioning feature enables package-level version control so that applications and applets can identify at runtime the version of a specific Java Runtime Environment, VM, and class package. For more information, see the Package Version Identification documentation.
Reference Objects
Reference objects support a limited degree of interaction with the garbage collector. A program may use a reference object to maintain a reference to some other object in such a way that the latter object may still be reclaimed by the collector. A program may also arrange to be notified some time after the collector has determined that the reachability of a given object has changed. Reference objects are therefore useful for building simple caches as well as caches that are flushed when memory runs low, for implementing mappings that do not prevent their keys (or values) from being reclaimed, and for scheduling pre-mortem cleanup actions in a more flexible way than is possible with the Java finalization mechanism. For more information, see the Reference Objects documentation.
Reflection enables Java code to discover information about the fields, methods and constructors of loaded classes, and to use reflected fields, methods, and constructors to operate on their underlying counterparts on objects, within security restrictions. The API accommodates applications that need access to either the public members of a target object (based on its runtime class) or the members declared by a given class. Programs can suppress default reflective access control. For more information, see the Reflection documentation.
Collections Framework
A collection is an object that represents a group of objects. The collections framework is a unified architecture for representing collections, allowing them to be manipulated independently of the details of their representation. It reduces programming effort while increasing performance. It allows for interoperability among unrelated APIs, reduces effort in designing and learning new APIs, and fosters software reuse. For more information, see the Collections Framework documentation.
Concurrency Utilities
The Concurrency Utilities packages provide a powerful, extensible framework of high-performance threading utilities such as thread pools and blocking queues. This package frees the programmer from the need to craft these utilities by hand, in much the same manner the Collections Framework did for data structures. Additionally, these packages provide low-level primitives for advanced concurrent programming. For more information, See the Concurrency Utilities documentation.
Java Archive (JAR) Files
JAR (Java Archive) is a platform-independent file format that aggregates many files into one. Multiple Java applets and their requisite components (.class files, images and sounds) can be bundled in a JAR file and subsequently downloaded to a browser in a single HTTP transaction, greatly improving the download speed. The JAR format also supports compression, which reduces the file size, further improving the download time. In addition, the applet author can digitally sign individual entries in a JAR file to authenticate their origin. It is fully extensible. For more information, see the Java Archive documentation.
The Logging APIs facilitate software servicing and maintenance at customer sites by producing log reports suitable for analysis by end users, system administrators, field service engineers, and software development teams. The Logging APIs capture information such as security failures, configuration errors, performance bottlenecks, and/or bugs in the application or platform. For more information, see the Logging documentation.
Preferences
The Preferences API provides a way for applications to store and retrieve user and system preference and configuration data. The data is stored persistently in an implementation-dependent backing store. There are two separate trees of preference nodes, one for user preferences and one for system preferences. For more information, see the Preferences API documentation,
Other Base Packages
The java.io and java.nio packages provide a rich set of APIs for managing an application’s I/O. The functionality includes file and device I/O, object serialization, buffer management, and character-set support. Additionally, the APIs support features for scalable servers including multiplexed, non-blocking I/O, memory mapping and locks for files. For more information, see the I/O documentation.
Object Serialization
Object Serialization extends the core Java Input/Output classes with support for objects. Object Serialization supports the encoding of objects, and the objects reachable from them, into a stream of bytes; and it supports the complementary reconstruction of the object graph from the stream. Serialization is used for lightweight persistence and for communication via sockets or Remote Method Invocation (RMI). See the Object Serialization documentation for more information.
Provides classes for networking functionality, including addressing, classes for using URLs and URIs, socket classes for connecting to servers, networking security functionality, and more. See the Networking documentation for more information.
APIs for security-related functionality such as configurable access control, digital signing, authentication and authorization, cryptography, secure Internet communication, and more. See the Security documentation for more information.
Internationalization
APIs that enable the development of internationalized applications. Internationalization is the process of designing an application so that it can be adapted to various languages and regions without engineering changes. See the Internationalization documentation for more information.
JavaBeans™ Component API
Contains classes related to developing beans — components based on the JavaBeans™ architecture that can be pieced together as part of developing an application. See the JavaBeans documentation for more information.
Java Management Extensions (JMX)
The Java Management Extensions (JMX) API is a standard API for management and monitoring of resources such as applications, devices, services, and the Java virtual machine. Typical uses include consulting and changing application configuration, accumulating statistics about application behavior, and notifying of state changes and erroneous conditions. The JMX API includes remote access, so a remote management program can interact with a running application for these purposes. See the Java Management Extensions documentation for more information.
The Java platform provides a rich set of APIs for processing XML documents and data. See the Java SE XML documentation for more information.
Java Native Interface (JNI)
Java Native Interface (JNI) is a standard programming interface for writing Java native methods and embedding the Java virtual machine into native applications. The primary goal is binary compatibility of native method libraries across all Java virtual machine implementations on a given platform. See the Java Native Interface documentation for more information.
Extension Mechanism
Optional packages are packages of Java classes (and any associated native code) that application developers can use to extend the functionality of the core platform. The extension mechanism allows the Java virtual machine (VM) to use the classes of the optional extension in much the same way as the VM uses classes in the Java Platform. The extension mechanism also provides a way for needed optional packages to be retrieved from specified URLs when they are not already installed in the JDK or Runtime Environment. See the Java Extension Mechanism documentation for more information.
Endorsed Standards Override Mechanism
An endorsed standard is a Java API defined through a standards process other than the Java Community ProcessSM (JCP). Because endorsed standards are defined outside the JCP, it is anticipated that such standards may be revised between releases of the Java Platform. In order to take advantage of new revisions to endorsed standards, developers and software vendors may use the Endorsed Standards Override Mechanism to provide newer versions of an endorsed standard than those included in the Java Platform as released by Oracle. See the Endorsed Standards Override Mechanism documentation for more information.
Integration Libraries
Java Database Connectivity (JDBC) API
The JDBC™ API provides universal data access from the Java programming language. Using the JDBC 3.0 API, you developers can write applications that can access virtually any data source, from relational databases to spreadsheets and flat files. JDBC technology also provides a common base on which tools and alternate interfaces can be built. For more information, see the JDBC documentation.
Remote Method Invocation (RMI)
Remote Method Invocation (RMI) enables the development of distributed applications by providing for remote communication between programs written in the Java programming language. RMI enables an object running in one Java Virtual Machine to invoke methods on an object running in another Java VM, which may be on a different host. For more information, see the Java SE RMI documentation.
Java IDL (CORBA)
Java IDL technology adds CORBA (Common Object Request Broker Architecture) capability to the Java platform, providing standards-based interoperability and connectivity. Java IDL enables distributed Web-enabled Java applications to transparently invoke operations on remote network services using the industry standard IDL (Object Management Group Interface Definition Language) and IIOP (Internet Inter-ORB Protocol) defined by the Object Management Group. Runtime components include a Java ORB for distributed computing using IIOP communication. For more information, see the Java IDL documentation.
RMI-IIOP
Java Remote Method Invocation over Internet Inter-ORB Protocol technology The RMI Programming Model enables the programming of CORBA servers and applications via the RMI API. You can choose to work completely within the Java programming language using the Java Remote Method Protocol (JRMP) as the transport, or work with other CORBA-compliant programming languages using the Internet InterORB Protocol (IIOP). You use the rmic compiler to generate the code necessary for connecting your applications via the Internet InterORB Protocol (IIOP) to others written in any CORBA-compliant language. To work with CORBA applications in other languages, IDL can be generated from Java programming language interfaces using the rmic compiler with the -idl option. To generate IIOP stubs and tie classes, use the rmic compiler with the -iiop option. For more information, see the RMI-IIOP documentation.
Scripting for the Java Platform
Java SE includes the JSR 223: Scripting for the Java™ Platform API. This is a framework by which Java Applications can «host» script engines. Java SE includes the Nashorn Engine, which is an implementation of the EMCAScript Edition 5.1 Language Specification. The scripting framework supports third-party script engines through jar «service discovery» mechanism. It is possible to «drop» any JSR-223 compliant script engine in the CLASSPATH and access the same from your Java applications For more information, see the Scripting documentation.
Java Naming and Directory Interface™ (JNDI) API
The Java Naming and Directory Interface™ (JNDI) provides naming and directory functionality to applications written in the Java programming language. It is designed to be independent of any specific naming or directory service implementation. Thus a variety of services—new, emerging, and already deployed ones—can be accessed in a common way. The JNDI architecture consists of a API and an SPI (Service Provider Interface). Java applications use this API to access a variety of naming and directory services. The SPI enables a variety of naming and directory services to be plugged in transparently, allowing the Java application using the JNDI API to access their services. For more information, see JNDI documentation.
User Interface Libraries
Input Method Framework
The input method framework enables the collaboration between text editing components and input methods in entering text. Input methods are software components that let the user enter text in ways other than simple typing on a keyboard. They are commonly used to enter Japanese, Chinese, or Korean — languages using thousands of different characters — on keyboards with far fewer keys. However, the framework also supports input methods for other languages and the use of entirely different input mechanisms, such as handwriting or speech recognition. For more information, see the Input Method Framework documentation.
Accessibility
With the Java Accessibility API, developers can easily create Java applications that are accessible to disabled persons. Accessible Java applications are compatible with assistive technologies such as screen readers, speech recognition systems, and refreshable braille displays. For more information, see the Accessibility documentation.
Print Service
The Java™ Print Service API, allows printing on all Java platforms including those requiring a small footprint, such as a Java ME profile. For more information, see Java Print Service documentation.
Sound
The Java platform includes a powerful API for capturing, processing, and playing back audio and MIDI (Musical Instrument Digital Interface) data. This API is supported by an efficient sound engine which guarantees high-quality audio mixing and MIDI synthesis capabilities for the platform. For more information, see Java Sound documentation.
Drag and Drop Data Transfer
Drag and Drop enables data transfer both across Java programming language and native applications, between Java programming language applications, and within a single Java programming language application. For more information, see Drag and Drop Transfer.
Image I/O
The Java Image I/O API provides a pluggable architecture for working with images stored in files and accessed across the network. The API provides a framework for the addition of format-specific plugins. Plug-ins for several common formats are included with Java Image I/O, but third parties can use this API to create their own plugins to handle special formats. For more information, see Image I/O.
Java 2D™ Graphics and Imaging
The Java 2D™ API is a set of classes for advanced 2D graphics and imaging. It encompasses line art, text, and images in a single comprehensive model. The API provides extensive support for image compositing and alpha channel images, a set of classes to provide accurate color space definition and conversion, and a rich set of display-oriented imaging operators. For more information, see the Java 2D documentation.
The Java™ platform’s Abstract Windowing Toolkit (AWT) provides APIs for constructing user interface components such as menus, buttons, text fields, dialog boxes, checkboxes, and for handling user input through those components. In addition, AWT allows for rendering of simple shapes such as ovals and polygons and enables developers to control the user-interface layout and fonts used by their applications. For more information, see the AWT documentation.
Swing
The Swing APIs also provide graphical component (GUI) for use in user interfaces. The Swing APIs are written in the Java programming language without any reliance on code that is specific to the GUI facilities provided by underlying operating system. This allows the Swing GUI components to have a «pluggable» look-and-feel that can be switched while an application is running. For more information, see the Java SE Swing documentation.
JavaFX
Java SE 7 Update 2 and later includes the JavaFX SDK. The JavaFX platform is the evolution of the Java client platform designed to enable application developers to easily create and deploy rich internet applications (RIAs) that behave consistently across multiple platforms. See JavaFX Documentation for more information.
Deployment
Java Deployment
Installation, setup, updating, redistribution and related topics:
- Installation of the Java Platform on a computer
- Setting Options in the Java Control Panel
- Writing applications and applets in the Java Programming language
- Authoring web pages that invoke applets or download and launch applications
- Making Java-related files available on web servers
- Updating the Java Platform on a computer
Tool Specifications
Debugger Architecture
Architecture and specifications for use by debuggers in development environments. For more information, see the Java Platform Debugger Architecture (JPDA) documentation.
VM Tool Interface
The Java Virtual Machine Tool Interface (JVM TI) is a specification for inspecting the state and controlling the execution of applications running in the JVM. The Java Virtual Machine Profiler Interface (JVMPI) has been deprecated. For more information, see the Java Virtual Machine Tool Interface (JVM TI) documentation.
Javadoc Tool
Javadoc is a tool that parses the declarations and documentation comments source files to produce a set of HTML pages describing the program elements. The Doclet API provides a mechanism for clients to inspect the source-level structure of programs and libraries, including Javadoc comments embedded in the source. This API can be used by doclets to generate documentation. For more information, see the Javadoc documentation.
Dynamic Attach
The package com.sun.tools.attach contains an Oracle extension to the Java Platform that allows an application to attach to a running Java virtual machine. Once the attach has been made, a tool agent can be started in the target virtual machine. For more information, see the attach documentation.
JConsole API
The package com.sun.tools.jconsole contains an Oracle extension to the Java Platform that provides a programmatic interface to access JConsole. For more information, see Using JConsole.
JDK Tools & Utilities
Documentation for the tools and utilities included in the JDK. Covers basic tools (javac, java, javadoc, apt, appletviewer, jar, jdb, javah, javap, extcheck), security tools, internationalization tools, RMI tools, IDL and RMI-IIOP tools, deployment tools, Java Plug-in tools, and Java Web Start tools, monitoring and management tools, and troubleshooting tools. For more information, see the JDK Tools and Utilities documentation.
Platforms
Oracle provides implementations of the JDK and Java Runtime Environment for Microsoft Windows, Linux, and the Solaris operating systems. See System Configurations for information about which versions of these platforms are supported.
Other companies may provide implementations of the Java platform for other operating systems such as Macintosh, AIX, etc.
Java se runtime environment что это
The Java Runtime Environment, or JRE, is a software layer that runs on top of a computer’s operating system software and provides the class libraries and other resources that a specific Java program needs to run.
The JRE is one of three interrelated components for developing and running Java programs. The other two components are as follows:
-
The Java Development Kit, or JDK, is a set of tools for developing Java applications. Developers choose JDKs by Java version and by package or edition—Java Enterprise Edition (Java EE), Java Special Edition (Java SE), or Java Mobile Edition (Java ME). Every JDK always includes a compatible JRE, because running a Java program is part of the process of developing a Java program.
The JRE combines Java code created using the JDK with the necessary libraries required to run it on a JVM and then creates an instance of the JVM that executes the resulting program. JVMs are available for multiple operating systems, and programs created with the JRE will run on all of them. In this way, the Java Runtime Environment is what enables a Java program to run in any operating system without modification.
The JDK and JRE interact with one another to create a sustainable runtime environment that enables the seamless execution of Java-based applications in virtually any operating system. The following make up the JRE runtime architecture:
ClassLoader
The Java ClassLoader dynamically loads all classes necessary to run a Java program. Since Java classes are only loaded into memory when they’re required, the JRE uses ClassLoaders to automate this process on demand.
Bytecode verifier
The bytecode verifier ensures the format and accuracy of Java code before it passes to the interpreter. In the event that code violates system integrity or access rights, the class will be considered corrupted and won’t be loaded.
Interpreter
After the bytecode successfully loads, the Java interpreter creates an instance of the JVM that allows the Java program to be executed natively on the underlying machine.
Besides the Java Virtual Machine, JRE is composed of a variety of other supporting software tools and features to get the most out of your Java applications.
Deployment solutions
Included as part of the JRE installation are deployment technologies like Java Web Start and Java Plugin that simplify the activation of applications and provide advanced support for future Java updates.
Development toolkits
The JRE also contains toolkits designed to help developers improve their user interface. Some of these toolkits include:
-
Java 2D: An Application Programming Interface (API) used for drawing two-dimensional graphics in Java language. Developers can create rich user interfaces, special effects, games, and animations.
Integration libraries
Java Runtime Environment provides a number of integration libraries to assist developers in creating seamless data connections between their applications and services. Some of these libraries include:
-
Java IDL (CORBA): Uses Common Object Request Architecture to support distributed objects written in Java programming language.
Language and utility libraries
Included with the JRE are java.lang. and java.util. packages that are fundamental for the design of Java applications, package versioning, management, and monitoring. Some of these packages include:
-
Collections Framework: A unified architecture made up of a collection of interfaces designed to improve the storage and process of application data.
Java se runtime environment что это
Java Runtime Environment (JRE) is an open-access software distribution that has a Java class library, specific tools, and a separate JVM. JRE is one of the interrelated components in the Java Development Kit (JDK). It is the most common environment available on devices for running Java programs. Java source code is compiled and converted to Java bytecode. If you want to run this bytecode on any platform, you need JRE. The JRE loads classes check memory access and get system resources. JRE acts as a software layer on top of the operating system.
Components of JRE
- Integration libraries include Java Database Connectivity (JDBC)
- Java Naming, Interface Definition Language (IDL)
- Directory Interface (JNDI)
- Remote Method Invocation Over Internet Inter-Orb Protocol (RMI-IIOP)
- Remote Method Invocation (RMI)
- Scripting
Java Virtual Machine (JVM) consists of Java HotSpot Client and Server Virtual Machine.
- User interface libraries include Swing, Java 2D, Abstract Window Toolkit (AWT), Accessibility, Image I/O, Print Service, Sound, drag, and drop (DnD), and input methods.
- Lang and util base libraries, which include lang and util, zip, Collections, Concurrency Utilities, management, Java Archive (JAR), instrument, reflection, versioning, Preferences API, Ref Objects, Logging, and Regular Expressions.
- Other base libraries, including Java Management Extensions (JMX), Java Native Interface (JNI), Math, Networking, international support, input/output (I/O), Beans, Java Override Mechanism, Security, Serialization, extension mechanism, and Java for XML Processing (XML JAXP).
- Deployment technologies such as Java Web Start, deployment, and Java plug-in.
Working of JRE
Java Development Kit (JDK) and Java Runtime Environment (JRE) both interact with each other to create a sustainable runtime environment that enables Java-based applications to run seamlessly on any operating system. The JRE runtime architecture consists of the following elements as listed:
Now let us brief about them as follows:
- ClassLoader: Java ClassLoader dynamically loads all the classes necessary to run a Java program. Because classes are only loaded into memory whenever they are needed, the JRE uses ClassLoader will automate this process when needed.
- Bytecode Verifier: The bytecode checker ensures the format and precision of Java code before passing it to the interpreter. If the code violates system integrity or access rights, the class is considered corrupt and will not load.
- Interpreter: After loading the byte code successfully, the Java interpreter creates an object of the Java virtual machine that allows the Java program to run natively on the underlying machine.
How does JRE work with JVM?
JRE has an object of JVM with it, development tools, and library classes. To understand the working of Java Runtime Environment let us see an example of a simple java program that prints “GeeksForGeeks”.
Что такое среда выполнения для Java?
Среда выполнения для Java (JRE) – это программное обеспечение, которое требуется для корректной работы программ Java. Java – это язык программирования, на котором написаны многие современные мобильные и интернет-приложения. JRE – это базовая технология, которая взаимодействует с Java-программой и операционной системой. Она действует как переводчик и посредник, предоставляя все ресурсы, чтобы после написания программного обеспечения на Java оно работало на любой операционной системе без дополнительных модификаций.
Почему JRE является столь важной?
Программе необходима среда выполнения, которая обеспечивает доступ к памяти и другим системным ресурсам, таким как программные файлы и зависимости. В прошлом большинство программ использовали непосредственно операционную систему в качестве среды выполнения. Однако это означало, что разработчикам приходилось писать отдельный код для каждой операционной системы, на которой они хотели, чтобы работали их приложения. Технология среды выполнения для Java (JRE) была создана как решение этой проблемы.
JRE – это один из трех компонентов платформы Java, которые необходимы для успешного выполнения любой программы на Java. Пакет средств разработки Java (JDK) и виртуальная машина Java (JVM) – это два других компонента.
Пакет средств разработки Java
JDK – это набор программных инструментов, которые можно использовать для разработки Java-приложений. Вы можете использовать JDK в своей среде разработки, скачав и установив его. Выберите версию программного обеспечения JDK, соответствующую версии Java, которую хотите использовать. Например, Java Standard Edition, или Java SE, требует Java SE JDK.
Виртуальная машина Java
JVM – это программное обеспечение, которое выполняет программу Java построчно. Разработчики настраивают параметры JVM для управления ресурсами программы при запуске Java-приложения. Например, вы можете изменить настройку памяти JVM и проверить, сколько внутренней памяти используют ваши Java-приложения во время выполнения.
Роль JRE в языке программирования Java
JRE объединяет код Java, который вы создаете с помощью JDK, с дополнительным встроенным кодом, называемым библиотеками. Затем он создает инстанс JVM или локальную копию, которая в конечном итоге запускает Java-программы. JVM доступны для множества операционных систем, а JRE генерирует единую копию вашего Java-кода, который работает на всех типах JVM. Таким образом, JRE обеспечивает платформенную независимость Java-приложений. Вы можете написать их один раз и запустить в любом месте.
Разница между JRE, JVM и JDK
JDK – это программный слой над JRE, который содержит компилятор, отладчик и другие инструменты, обычно встречающиеся в любой среде разработки программного обеспечения. В JDK вы пишете код с использованием синтаксиса, подобного английскому языку. JDK компилирует его и передает байт-код в JRE. В отличие от этого, JRE содержит библиотеки классов, вспомогательные файлы и JVM. Здесь используются эти программные компоненты для запуска байт-кода на любом устройстве.
Как работает JRE?
Среда выполнения Java (JRE) работает поверх операционной системы, предоставляя дополнительные ресурсы, специфичные для Java. Пакет средств разработки Java (JDK) и JRE взаимодействуют для создания устойчивой среды выполнения, которая запускает программные файлы Java на любой машине. JRE использует для работы три основных компонента.
ClassLoader
Библиотеки классов Java содержат коллекции заранее написанного кода, который можно вызывать по мере необходимости. Они упрощают работу Java-разработчиков, предоставляя встроенные методы для таких распространенных и нетривиальных задач, как прием входных данных от пользователей, отображение выходных данных для пользователей и многое другое. Все программы на Java ссылаются на несколько библиотек классов. Java ClassLoader динамически загружает все необходимые файлы классов в виртуальную машину Java (JVM) по требованию.
Верификатор байткода
В JDK есть компилятор, который преобразует написанный вами англоязычный код в версию на машинном языке, называемую байткодом Java. Верификатор байткода в JRE проверяет формат и точность кода Java перед его загрузкой в JVM. Например, если код нарушает целостность системы или права доступа, JRE не загрузит файл класса.
Переводчик
После успешной загрузки байткода интерпретатор Java создает инстанс JVM, который запускает программу Java на базовой машине.
Из каких компонентов состоит JRE?
Помимо основных компонентов, среда выполнения для Java (JRE) содержит несколько других программных компонентов, которые помогают более эффективно выполнять Java-программы. Далее приведены некоторые примеры.
Инструменты разработки
JRE содержит средства разработки, такие как наборы инструментов пользовательского интерфейса, которые можно использовать для улучшения качества ваших приложений. Далее приведены некоторые примеры.
Java 2D
Java 2D – это интерфейс прикладных задач (API), который можно использовать для рисования двумерной графики и создания прекрасных пользовательских интерфейсов, игр, анимации и специальных эффектов на языке Java.
Swing
Swing – это легкий графический интерфейс пользователя (GUI), который обеспечивает гибкую, удобную для пользователя настройку.
Abstract Window Toolkit
Abstract Window Toolkit (AWT) – это графический интерфейс, который можно использовать для создания объектов пользовательского интерфейса, таких как кнопки, окна и полосы прокрутки.
Решения по развертыванию
JRE включает технологии, которые упрощают процесс выпуска изменений программного обеспечения для пользователей приложений. Эти технологии также обеспечивают расширенную поддержку обновлений в приложении. Технологии развертывания, такие как Java Web Start и плагин Java, включены как часть установки JRE. Эти технологии упрощают активацию приложений, а также обеспечивают расширенную поддержку будущих обновлений JRE. Далее приведены некоторые примеры.
Java Web Start
С помощью Java Web Start вы можете запускать полнофункциональные приложения одним щелчком мыши из веб-браузера.
Плагин Java
Плагин Java устанавливает соединение между популярными браузерами и платформой Java, что позволяет запускать апплеты в браузерах для настольных компьютеров.
Библиотеки языков и утилит
Коллекция файлов классов Java называется пакетом Java. JRE включает несколько пакетов Java, которые поддерживают версионность, управление и мониторинг. В качестве примера можно привести следующие пакеты:
Система коллекций
Система коллекций представляет собой единую архитектуру, включающую интерфейсы для улучшения хранения и обработки данных приложений.
API предпочтений
API предпочтений позволяет нескольким пользователям на одной машине определять собственную группу предпочтений приложений.
Ведение журналов
С помощью пакетов журналов создаются отчеты журналов для устранения неисправностей, таких как сбои в системе безопасности, проблемы с производительностью и ошибки конфигурации.
Архив Java
Архив Java (JAR) – это независимый от платформы формат файлов, позволяющий объединять несколько файлов для уменьшения размера файлов приложений и значительного повышения скорости загрузки.
Интеграционные библиотеки
JRE включает несколько интеграционных библиотек, которые помогают разработчикам создавать удобные соединения данных между сервисами и приложениями. Ниже приведены некоторые примеры библиотек.
Java IDL
Язык Java Interface Definition Language (IDL), который основан на архитектуре Common Object Request Broker Architecture (CORBA), поддерживает распределенные объекты данных, то есть объекты, которые взаимодействуют на разных платформах по сети. Например, Java IDL позволяет объектам, написанным на Java, взаимодействовать с объектами, написанными на другом языке, таком как C, C++ или COBOL.
Подключение к базам данных Java
Разработчики используют API Java Database Connectivity (JDBC) для написания приложений, которые могут обращаться к удаленным базам данных, электронным таблицам и файлам.
Java Naming and Directory Interface
Java Naming and Directory Interface (JNDI) – это сервис каталогов, позволяющий клиентам создавать переносимые приложения, которые получают информацию из внешних баз данных, используя правила именования.
Что такое AWS SDK для Java?
Пакет средств разработки ПО (SDK) AWS для Java упрощает использование сервисов AWS, предоставляя упорядоченный набор библиотек, с которыми знакомы разработчики Java. AWS SDK for Java также поддерживает более высокий уровень абстракций для упрощения разработки. Доступны библиотеки Java с открытым исходным кодом, ориентированные на AWS, а также примеры кода и справочное руководство по API Java.
Примеры кода AWS SDK для Java 2.0 на GitHub содержат примеры на языке Java и реальные примеры работы с сервисами AWS, которые ускорят разработку собственных приложений. Кроме того, справочник AWS SDK по Java API описывает работу API в новейшей версии AWS SDK для Java. Кроме того, приводятся образцы запросов, ответов и список ошибок для поддерживаемых сетевых протоколов.