JDK-4695200 : ByteArrayInputStream doesn't specify behavior when mark(readlimit) is used
  • Type: Bug
  • Component: docs
  • Sub-Component: guides
  • Affected Version: 1.4.0,5.0
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,solaris_2.6
  • CPU: generic,sparc
  • Submitted: 2002-05-31
  • Updated: 2017-05-16
  • Resolved: 2003-11-11
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 b28Fixed
Description
Name: asR10047			Date: 05/31/2002


ByteArrayInputStream extended from InputStream overrides mark(int readLimit)
method but does not comment how it's behaviour changes depending on
readLimit value.

There is only one sentence that states "readAheadLimit - the maximum limit of
bytes that can be read before the mark position becomes invalid." but all
other comments and actual behaviour don't support it.

I regard it as the specification bug. Specification should clarify how
readAheadLimit influences on reset() and mark() or should states readAheadLimit
is not used by ByteArrayInputStream.

Please note, current implementation does not take into account readAheadLimit
value at all.

======================================================================
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic tiger-beta FIXED IN: tiger tiger-beta INTEGRATED IN: tiger-b28 tiger-beta VERIFIED IN: 1.5
14-09-2004
EVALUATION Will add the following note to the comment in question: * <p> The <code>readAheadLimit</code> for class * <code>ByteArrayInputStream</code> has no meaning. ###@###.### 2003-09-17
17-09-2003