P4
FULL PRODUCT VERSION :
java version "1.4.2_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06)
Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode)
FULL OS VERSION :
Microsoft Windows XP [Version 5.1.2600]
A DESCRIPTION OF THE PROBLEM :
This is a documentation bug. The Throwable class includes the following API doc comment.
For example, suppose a persistent collection conforms to the Collection interface, and that its persistence is implemented atop java.io. Suppose the internals of the put method can throw an IOException. The implementation can communicate the details of the IOException to its caller while conforming to the Collection interface by wrapping the IOException in an appropriate unchecked exception. (The specification for the persistent collection should indicate that it is capable of throwing such exceptions.)
This is supposed to be an example of why it is sometimes necessary to use exception chaining because of the compile-enforced method contract. It makes no sense, however, because there is no put method in the Collection interface. The only put method this API doc comment can be referring is part of the ObjectOutputStream.PutField inner class.
REPRODUCIBILITY :
This bug can be reproduced always.
###@###.### 2005-1-29 01:39:20 GMT
java version "1.4.2_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06)
Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode)
FULL OS VERSION :
Microsoft Windows XP [Version 5.1.2600]
A DESCRIPTION OF THE PROBLEM :
This is a documentation bug. The Throwable class includes the following API doc comment.
For example, suppose a persistent collection conforms to the Collection interface, and that its persistence is implemented atop java.io. Suppose the internals of the put method can throw an IOException. The implementation can communicate the details of the IOException to its caller while conforming to the Collection interface by wrapping the IOException in an appropriate unchecked exception. (The specification for the persistent collection should indicate that it is capable of throwing such exceptions.)
This is supposed to be an example of why it is sometimes necessary to use exception chaining because of the compile-enforced method contract. It makes no sense, however, because there is no put method in the Collection interface. The only put method this API doc comment can be referring is part of the ObjectOutputStream.PutField inner class.
REPRODUCIBILITY :
This bug can be reproduced always.
###@###.### 2005-1-29 01:39:20 GMT