|
FlexDoc/Javadoc 2.0 Demo Java Doc |
Terminally Deprecated Elements |
It is rarely appropriate to use this constructor. The static factory
Boolean.valueOf(boolean) is generally a better choice, as it is
likely to yield significantly better space and time performance.
Also consider using the final fields Boolean.TRUE and Boolean.FALSE
if possible.
|
It is rarely appropriate to use this constructor.
Use Boolean.parseBoolean(String) to convert a string to a
boolean primitive, or use Boolean.valueOf(String)
to convert a string to a Boolean object.
|
It is rarely appropriate to use this constructor. The static factory
Byte.valueOf(byte) 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.
Use Byte.parseByte(String) to convert a string to a
byte primitive, or use Byte.valueOf(String)
to convert a string to a Byte object.
|
It is rarely appropriate to use this constructor. The static factory
Character.valueOf(char) is generally a better choice, as it is
likely to yield significantly better space and time performance.
|
JIT compilers and their technologies vary too widely to
be controlled effectively by a standardized interface. As such, many
JIT compiler implementations ignore this interface, and are instead
controllable by implementation-specific mechanisms such as command-line
options. This class is subject to removal in a future version of Java SE.
|
It is rarely appropriate to use this constructor. The static factory
Double.valueOf(double) 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.
Use Double.parseDouble(String) to convert a string to a
double primitive, or use Double.valueOf(String)
to convert a string to a Double object.
|
It is rarely appropriate to use this constructor. Instead, use the
static factory method Float.valueOf(float) method as follows:
Float.valueOf((float)value).
|
It is rarely appropriate to use this constructor. The static factory
Float.valueOf(float) 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.
Use Float.parseFloat(String) to convert a string to a
float primitive, or use Float.valueOf(String)
to convert a string to a Float object.
|
It is rarely appropriate to use this constructor. The static factory
Integer.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.
Use Integer.parseInt(String) to convert a string to a
int primitive, or use Integer.valueOf(String)
to convert a string to an Integer object.
|
It is rarely appropriate to use this constructor. The static factory
Long.valueOf(long) 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.
Use Long.parseLong(String) to convert a string to a
long primitive, or use Long.valueOf(String)
to convert a string to a Long object.
|
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
Short.valueOf(short) 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.
Use Short.parseShort(String) to convert a string to a
short primitive, or use Short.valueOf(String)
to convert a string to a Short object.
|
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.
|
This method was originally designed to count the number of
stack frames but the results were never well-defined and it
depended on thread-suspension.
This method is subject to removal in a future version of Java SE.
|
This method exists solely for use with Thread.suspend(),
which has been deprecated because it is deadlock-prone.
For more information, see
Why
are Thread.stop, Thread.suspend and Thread.resume Deprecated?.
|
This method has been deprecated, as it is
inherently deadlock-prone. If the target thread holds a lock on the
monitor protecting a critical system resource when it is suspended, no
thread can access this resource until the target thread is resumed. If
the thread that would resume the target thread attempts to lock this
monitor prior to calling resume, deadlock results. Such
deadlocks typically manifest themselves as "frozen" processes.
For more information, see
Why
are Thread.stop, Thread.suspend and Thread.resume Deprecated?.
|
The definition of this call depends on ThreadGroup.suspend(),
which is deprecated. Further, the behavior of this call
was never specified.
|
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.
|
The API and mechanism for destroying a ThreadGroup is inherently
flawed. The ability to explicitly or automatically destroy a
thread group will be removed in a future release.
|
The API and mechanism for destroying a ThreadGroup is inherently
flawed. The ability to explicitly or automatically destroy a
thread group, and the concept of daemon thread group, will be
removed in a future release.
|
The API and mechanism for destroying a ThreadGroup is inherently
flawed. The ability to explicitly or automatically destroy a
thread group will be removed in a future release.
|
This method is used solely in conjunction with
Thread.suspend and ThreadGroup.suspend,
both of which have been deprecated, as they are inherently
deadlock-prone. See Thread.suspend() for details.
|
The API and mechanism for destroying a ThreadGroup is inherently
flawed. The ability to explicitly or automatically destroy a
thread group, and the concept of daemon thread group, will be
removed in a future release.
|
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.
|
Deprecated Interfaces |
Deprecated Classes |
This class incorrectly assumes that bytes adequately represent
characters. As of JDK 1.1, the preferred way to operate on
character streams is via the new character-stream classes, which
include a class for counting line numbers.
|
This class does not properly convert characters into bytes. As
of JDK 1.1, the preferred way to create a stream from a
string is via the StringReader class.
|
JIT compilers and their technologies vary too widely to
be controlled effectively by a standardized interface. As such, many
JIT compiler implementations ignore this interface, and are instead
controllable by implementation-specific mechanisms such as command-line
options. This class is subject to removal in a future version of Java SE.
|
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.
|
This class and the Observer interface have been deprecated.
The event model supported by Observer and Observable
is quite limited, the order of notifications delivered by
Observable is unspecified, and state changes are not in
one-for-one correspondence with notifications.
For a richer event model, consider using the
java.beans package. For reliable and ordered
messaging among threads, consider using one of the concurrent data
structures in the java.util.concurrent package.
For reactive streams style programming, see the
Flow API.
|
Deprecated Constructors |
It is rarely appropriate to use this constructor. The static factory
Boolean.valueOf(boolean) is generally a better choice, as it is
likely to yield significantly better space and time performance.
Also consider using the final fields Boolean.TRUE and Boolean.FALSE
if possible.
|
It is rarely appropriate to use this constructor.
Use Boolean.parseBoolean(String) to convert a string to a
boolean primitive, or use Boolean.valueOf(String)
to convert a string to a Boolean object.
|
It is rarely appropriate to use this constructor. The static factory
Byte.valueOf(byte) 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.
Use Byte.parseByte(String) to convert a string to a
byte primitive, or use Byte.valueOf(String)
to convert a string to a Byte object.
|
It is rarely appropriate to use this constructor. The static factory
Character.valueOf(char) is generally a better choice, as it is
likely to yield significantly better space and time performance.
|
As of JDK version 1.1,
replaced by Calendar.set(year + 1900, month, date)
or GregorianCalendar(year + 1900, month, date).
|
As of JDK version 1.1,
replaced by Calendar.set(year + 1900, month, date, hrs, min)
or GregorianCalendar(year + 1900, month, date, hrs, min).
|
As of JDK version 1.1,
replaced by Calendar.set(year + 1900, month, date, hrs, min, sec)
or GregorianCalendar(year + 1900, month, date, hrs, min, sec).
|
As of JDK version 1.1,
replaced by DateFormat.parse(String s).
|
It is rarely appropriate to use this constructor. The static factory
Double.valueOf(double) 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.
Use Double.parseDouble(String) to convert a string to a
double primitive, or use Double.valueOf(String)
to convert a string to a Double object.
|
It is rarely appropriate to use this constructor. Instead, use the
static factory method Float.valueOf(float) method as follows:
Float.valueOf((float)value).
|
It is rarely appropriate to use this constructor. The static factory
Float.valueOf(float) 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.
Use Float.parseFloat(String) to convert a string to a
float primitive, or use Float.valueOf(String)
to convert a string to a Float object.
|
It is rarely appropriate to use this constructor. The static factory
Integer.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.
Use Integer.parseInt(String) to convert a string to a
int primitive, or use Integer.valueOf(String)
to convert a string to an Integer object.
|
It is rarely appropriate to use this constructor. The static factory
Long.valueOf(long) 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.
Use Long.parseLong(String) to convert a string to a
long primitive, or use Long.valueOf(String)
to convert a string to a Long object.
|
It is rarely appropriate to use this constructor. The static factory
Short.valueOf(short) 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.
Use Short.parseShort(String) to convert a string to a
short primitive, or use Short.valueOf(String)
to convert a string to a Short object.
|
As of JDK version 1.1, the preferred way to tokenize an
input stream is to convert it into a character stream, for example:
Reader r = new BufferedReader(new InputStreamReader(is));
StreamTokenizer st = new StreamTokenizer(r);
|
This method does not properly convert bytes into
characters. As of JDK 1.1, the preferred way to do this is via the
String constructors that take a Charset, charset name, or that use the platform's
default charset.
|
This method does not properly convert bytes into characters.
As of JDK 1.1, the preferred way to do this is via the
String constructors that take a Charset, charset name, or that use the platform's
default charset.
|
|
FlexDoc/Javadoc 2.0 Demo Java Doc |