![]() Future JEPs or enhancements may define new APIs or mechanisms for specific use cases, depending upon demand. It is not a goal to provide a replacement for the Security Manager. Warn users if their Java applications rely on the Security Manager.Įvaluate whether new APIs or mechanisms are needed to address specific narrow use cases for which the Security Manager has been employed, such as blocking System::exit. Prepare developers for the removal of the Security Manager in a future version of Java. ![]() To move Java forward, we intend to deprecate the Security Manager for removal in concert with the legacy Applet API ( JEP 398). It has not been the primary means of securing client-side Java code for many years, and it has rarely been used to secure server-side code. The Security Manager dates from Java 1.0. ![]() Deprecate the Security Manager for removal in a future release.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |