2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work? 2.9 Are there any internationalization or localization issues? 2.8 Are there any security issues that cannot be addressed by the current security model? 2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of? 2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.) 2.5 Please give a short description of the underlying technology or technologies: The majority of the existing monitoring and management options andĪre very limited, lack functionality, degrade performance, and areĪnd non standard, leading to a multitude of disconnected solutions. 2.4 Why isn't this need met by existing specifications? Monitoring and management from within Java applications as well as remoteīy system management applications and RAS-related tools. This specification is intended to provide the underlying support for Java 2 Standard Edition 2.3 What need of the Java community will be addressed by the proposed specification? Which appears to have some functional overlap with the health indicators.Ĭonflicting requirements do not preclude a single interface, one will beĭeveloped in concert with the JSR-163 Expert Group.Ģ.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.) Support for existing system management standards such as JMX andĪ new Java TM Platform Profiling Architecture is being developed Requiring minimal perturbation of the system. Monitoring of Java applications as well as native interfaces to support These characteristics suggest the need for Java APIs to support self
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |