Name: saf@russia Date: 09/09/96


This bug was found by St.Petersburg Java SQE team (by Stanislav Avzan).

The Java Language specification (Version 1.0 - August 1, 1996) does not describe
behaviour of java.io.PipedInputStream/PipedOutputStream class methods in case
of unconnected streams.

In fact, unconnected PipedInputStream behaves as empty connected closed from
PipedOutputStream side PipedInputStream eg. any reading returns -1 (EOF marker).

Unconnected PipedOutputStream throws NullPointerException by any writing.

We suppose both PipedInputStream and PipedOutputStream should throw IOException
in case of unconnected streams. If so, source code revision should be made.

Workaround:
None
======================================================================