Deprecated API

The Motif Look and Feel is deprecated with the intent to remove it in some future release. It is recommended to use javax.swing.plaf.metal.MetalLookAndFeel instead.

The sensitivity levels were historically used by polling-based WatchService implementations to configure the polling interval. They are are no longer used. The WatchService implementations in the JDK ignore these WatchEvent modifiers if they are specified when registering a directory to be watched.

The Applet API is deprecated, no replacement.

The Applet API is deprecated, no replacement.

Finalization has been deprecated for removal. See java.lang.Object#finalize for background information and details about migration options.

The Applet API is deprecated. See the java.applet package documentation for further information.

It is recommended to use instantiate(ClassLoader, String, BeanContext), because the Applet API is deprecated. See the java.applet package documentation for further information.

This method does not write the values contained by this PutField object in a proper format, and may result in corruption of the serialization stream. The correct way to write PutField data is by calling the java.io.ObjectOutputStream#writeFields() method.

It is rarely appropriate to use this constructor. Use parseBoolean(String) to convert a string to a boolean primitive, or use valueOf(String) to convert a string to a Boolean object.

It is rarely appropriate to use this constructor. Use parseByte(String) to convert a string to a byte primitive, or use valueOf(String) to convert a string to a Byte object.

It is rarely appropriate to use this constructor. The static factory valueOf(double) is generally a better choice, as it is likely to yield significantly better space and time performance.

Finalization has been deprecated for removal. See java.lang.Object#finalize for background information and details about migration options.

It is rarely appropriate to use this constructor. Instead, use the static factory method valueOf(float) method as follows: Float.valueOf((float)value).

It is rarely appropriate to use this constructor. The static factory valueOf(int) is generally a better choice, as it is likely to yield significantly better space and time performance.

It is rarely appropriate to use this constructor. The static factory valueOf(long) is generally a better choice, as it is likely to yield significantly better space and time performance.

Finalization is deprecated and subject to removal in a future release. The use of finalization can lead to problems with security, performance, and reliability. See JEP 421 for discussion and alternatives.

Subclasses that override finalize to perform cleanup should use alternative cleanup mechanisms and remove the finalize method. Use java.lang.ref.Cleaner and java.lang.ref.PhantomReference as safer ways to release resources when an object becomes unreachable. Alternatively, add a close method to explicitly release resources, and implement AutoCloseable to enable use of the try-with-resources statement.

This method will remain in place until finalizers have been removed from most existing code.

The Security Manager is deprecated and subject to removal in a future release. There is no replacement for the Security Manager. See JEP 411 for discussion and alternatives.

It is rarely appropriate to use this constructor. The static factory valueOf(short) is generally a better choice, as it is likely to yield significantly better space and time performance.

This method is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this method is also deprecated and subject to removal. There is no replacement for the Security Manager or this method.

This method is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this method is also deprecated and subject to removal. There is no replacement for the Security Manager or this method.

This method was originally specified to "stop" a victim thread by causing the victim thread to throw a ThreadDeath. It was inherently unsafe. Stopping a thread caused it to unlock all of the monitors that it had locked (as a natural consequence of the ThreadDeath exception propagating up the stack). If any of the objects previously protected by these monitors were in an inconsistent state, the damaged objects became visible to other threads, potentially resulting in arbitrary behavior. Usages of stop should be replaced by code that simply modifies some variable to indicate that the target thread should stop running. The target thread should check this variable regularly, and return from its run method in an orderly fashion if the variable indicates that it is to stop running. If the target thread waits for long periods (on a condition variable, for example), the interrupt method should be used to interrupt the wait. For more information, see Why is Thread.stop deprecated and the ability to stop a thread removed?.

This method is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this method is also deprecated and subject to removal. There is no replacement for the Security Manager or this method.

This method originally indicated if the thread group is a daemon thread group that is automatically destroyed when its last thread terminates. The concept of daemon thread group no longer exists. A thread group is eligible to be GC'ed when there are no live threads in the group and it is otherwise unreachable.

This method originally configured whether the thread group is a daemon thread group that is automatically destroyed when its last thread terminates. The concept of daemon thread group no longer exists. A thread group is eligible to be GC'ed when there are no live threads in the group and it is otherwise unreachable.

use setTimeToLive instead.

Use the following code or its equivalent instead:

......
 int ttl = mcastSocket.getOption(StandardSocketOptions.IP_MULTICAST_TTL);
 mcastSocket.setOption(StandardSocketOptions.IP_MULTICAST_TTL, newttl);
 mcastSocket.send(p);
 mcastSocket.setOption(StandardSocketOptions.IP_MULTICAST_TTL, ttl);
 ......

Use DatagramSocket instead for UDP transport.

This class is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this class is also deprecated and subject to removal. There is no replacement for the Security Manager or this class.

This class is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this class is also deprecated and subject to removal. There is no replacement for the Security Manager or this class.

This class is deprecated and subject to removal in a future version of Java SE. It has been replaced by java.security.cert.Certificate and related classes.

This class is deprecated and subject to removal in a future version of Java SE. It has been replaced by java.security.KeyStore, the java.security.cert package, and java.security.Principal.

This class is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this class is also deprecated and subject to removal. There is no replacement for the Security Manager or this class.

This class is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this class is also deprecated and subject to removal. There is no replacement for the Security Manager or this class.

This method is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this method is also deprecated and subject to removal. There is no replacement for the Security Manager or this method.

This method is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this method is also deprecated and subject to removal. There is no replacement for the Security Manager or this method.

This method is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this method is also deprecated and subject to removal. There is no replacement for the Security Manager or this method.

Finalization has been deprecated for removal. See java.lang.Object#finalize for background information and details about migration options.

Finalization has been deprecated for removal. See java.lang.Object#finalize for background information and details about migration options.

Finalization has been deprecated for removal. See java.lang.Object#finalize for background information and details about migration options.

This method supported the legacy Subject Delegation feature, which has been removed. There is no replacement.

The getPeerCertificates() method that returns an array of java.security.cert.Certificate should be used instead.

This method depends on AccessControlContext which, in conjunction with the Security Manager, is deprecated and subject to removal in a future release. However, performing work as a Subject is useful independent of the Security Manager. Thus, a replacement API named callAs has been added which can be used to perform the same work.

This method is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this method is also deprecated and subject to removal. There is no replacement for the Security Manager or this method.

This method depends on AccessControlContext which, in conjunction with the Security Manager, is deprecated and subject to removal in a future release. However, obtaining a Subject is useful independent of the Security Manager. Thus, a replacement API named current() has been added which can be used to obtain the current subject.

Use the classes in java.security.cert instead.

Use the classes in java.security.cert instead.

Use the classes in java.security.cert instead.

Use the classes in java.security.cert instead.

The Applet API is deprecated. See the java.applet package documentation for further information.

Obsolete method, not used anymore.

It is recommended that BasicToolBarUI#createFloatingWindow(JToolBar) be used instead

The Applet API is deprecated. See the java.applet package documentation for further information.

Not needed when using VarHandle or java.lang.foreign.

Not needed when using VarHandle or java.lang.foreign.

Not needed when using VarHandle or java.lang.foreign.

Not needed when using VarHandle or java.lang.foreign.

Not needed when using VarHandle or java.lang.foreign.

Not needed when using VarHandle or java.lang.foreign.

Not needed when using VarHandle or java.lang.foreign.

Not needed when using VarHandle or java.lang.foreign.

Not needed when using VarHandle or java.lang.foreign.

Not needed when using VarHandle or java.lang.foreign.

Use java.lang.foreign to allocate off-heap memory.

Not needed when using VarHandle or java.lang.foreign.

Use VarHandle#compareAndExchange(Object...) instead.

Use MemorySegment and its bulk copy methods instead.

Use java.lang.foreign to allocate and free off-heap memory.

Use java.lang.foreign to access off-heap memory.

Use VarHandle#getAndAdd(Object...) instead.

Use VarHandle#getAndAdd(Object...) instead.

Use VarHandle#get(Object...) or MemorySegment#get(ValueLayout.OfBoolean, long) instead.

Use VarHandle#get(Object...) or MemorySegment#get(ValueLayout.OfByte, long) instead.

Use VarHandle#getVolatile(Object...) instead.

Use java.lang.foreign to access off-heap memory.

Use VarHandle#get(Object...) or MemorySegment#get(ValueLayout.OfDouble, long) instead.

Use VarHandle#getVolatile(Object...) instead.

Use java.lang.foreign to access off-heap memory.

Use VarHandle#get(Object...) or MemorySegment#get(ValueLayout.OfInt, long) instead.

Use VarHandle#getVolatile(Object...) instead.

Use VarHandle#get(Object...) or MemorySegment#get(ValueLayout.OfLong, long) instead.

Use VarHandle#getVolatile(Object...) instead.

Use VarHandle#getVolatile(Object...) instead.

Use java.lang.foreign to access off-heap memory.

Use a MemorySegment allocated in an Arena with the appropriate temporal bounds. The MemorySegment#asByteBuffer() method wraps a memory segment as a ByteBuffer to allow interop with existing code.

The guarantee that a field will always have the same offset and base may not be true in a future release. The ability to provide an offset and object reference to a heap memory accessor will be removed in a future release. Use VarHandle instead.

Use java.lang.foreign to access off-heap memory.

Use VarHandle#setVolatile(Object...) instead.

Use java.lang.foreign to access off-heap memory.

Use VarHandle#set(Object...) or MemorySegment#set(ValueLayout.OfChar, long, char) instead.

Use VarHandle#setVolatile(Object...) instead.

Use java.lang.foreign to access off-heap memory.

Use VarHandle#set(Object...) or MemorySegment#set(ValueLayout.OfFloat, long, float) instead.

Use VarHandle#setVolatile(Object...) instead.

Use java.lang.foreign to access off-heap memory.

Use VarHandle#set(Object...) or MemorySegment#set(ValueLayout.OfLong, long, long) instead.

Use VarHandle#setVolatile(Object...) instead.

Use VarHandle#setVolatile(Object...) instead.

Use VarHandle#setRelease(Object...) instead.

Use VarHandle#set(Object...) or MemorySegment#set(ValueLayout.OfShort, long, short) instead.

Use VarHandle#setVolatile(Object...) instead.

MemorySegment#fill(byte) fills the contents of a memory segment with a given value.

The guarantee that a field will always have the same offset and base may not be true in a future release. The ability to provide an offset and object reference to a heap memory accessor will be removed in a future release. Use VarHandle instead.

Use VarHandle#releaseFence() instead.