Class FileOutputStream
- All Implemented Interfaces:
Closeable,Flushable,AutoCloseable
public class FileOutputStream extends OutputStream
File file = ...
OutputStream out = null;
try {
out = new BufferedOutputStream(new FileOutputStream(file));
...
} finally {
if (out != null) {
out.close();
}
}
This stream is not buffered. Most callers should wrap
this stream with a BufferedOutputStream.
Use FileWriter to write characters, as opposed to bytes, to a file.
- See Also:
BufferedOutputStream,FileInputStream
-
Constructor Summary
Constructors Constructor Description FileOutputStream(File file)Constructs a newFileOutputStreamthat writes tofile.FileOutputStream(FileDescriptor fd)Constructs a newFileOutputStreamthat writes tofd.FileOutputStream(File file, boolean append)Constructs a newFileOutputStreamthat writes tofile.FileOutputStream(String path)Constructs a newFileOutputStreamthat writes topath.FileOutputStream(String path, boolean append)Constructs a newFileOutputStreamthat writes topath. -
Method Summary
Modifier and Type Method Description voidclose()Closes this stream.protected voidfinalize()Invoked when the garbage collector has detected that this instance is no longer reachable.FileChannelgetChannel()Returns a write-onlyFileChannelthat shares its position with this stream.FileDescriptorgetFD()Returns the underlying file descriptor.voidwrite(byte[] buffer, int byteOffset, int byteCount)Writescountbytes from the byte arraybufferstarting at positionoffsetto this stream.voidwrite(int oneByte)Writes a single byte to this stream.Methods inherited from class java.io.OutputStream
flush, write
-
Constructor Details
-
FileOutputStream
Constructs a newFileOutputStreamthat writes tofile. The file will be truncated if it exists, and created if it doesn't exist.- Throws:
FileNotFoundException- if file cannot be opened for writing.
-
FileOutputStream
Constructs a newFileOutputStreamthat writes tofile. Ifappendis true and the file already exists, it will be appended to; otherwise it will be truncated. The file will be created if it does not exist.- Throws:
FileNotFoundException- if the file cannot be opened for writing.
-
FileOutputStream
Constructs a newFileOutputStreamthat writes tofd.- Throws:
NullPointerException- iffdis null.
-
FileOutputStream
Constructs a newFileOutputStreamthat writes topath. The file will be truncated if it exists, and created if it doesn't exist.- Throws:
FileNotFoundException- if file cannot be opened for writing.
-
FileOutputStream
Constructs a newFileOutputStreamthat writes topath. Ifappendis true and the file already exists, it will be appended to; otherwise it will be truncated. The file will be created if it does not exist.- Throws:
FileNotFoundException- if the file cannot be opened for writing.
-
-
Method Details
-
close
Description copied from class:OutputStreamCloses this stream. Implementations of this method should free any resources used by the stream. This implementation does nothing.- Specified by:
closein interfaceAutoCloseable- Specified by:
closein interfaceCloseable- Overrides:
closein classOutputStream- Throws:
IOException- if an error occurs while closing this stream.
-
finalize
Description copied from class:ObjectInvoked when the garbage collector has detected that this instance is no longer reachable. The default implementation does nothing, but this method can be overridden to free resources.Note that objects that override
finalizeare significantly more expensive than objects that don't. Finalizers may be run a long time after the object is no longer reachable, depending on memory pressure, so it's a bad idea to rely on them for cleanup. Note also that finalizers are run on a single VM-wide finalizer thread, so doing blocking work in a finalizer is a bad idea. A finalizer is usually only necessary for a class that has a native peer and needs to call a native method to destroy that peer. Even then, it's better to provide an explicitclosemethod (and implementCloseable), and insist that callers manually dispose of instances. This works well for something like files, but less well for something like aBigIntegerwhere typical calling code would have to deal with lots of temporaries. Unfortunately, code that creates lots of temporaries is the worst kind of code from the point of view of the single finalizer thread.If you must use finalizers, consider at least providing your own
ReferenceQueueand having your own thread process that queue.Unlike constructors, finalizers are not automatically chained. You are responsible for calling
super.finalize()yourself.Uncaught exceptions thrown by finalizers are ignored and do not terminate the finalizer thread. See Effective Java Item 7, "Avoid finalizers" for more.
- Overrides:
finalizein classObject- Throws:
IOException
-
getChannel
Returns a write-onlyFileChannelthat shares its position with this stream. -
getFD
Returns the underlying file descriptor.- Throws:
IOException
-
write
Description copied from class:OutputStreamWritescountbytes from the byte arraybufferstarting at positionoffsetto this stream.- Overrides:
writein classOutputStream- Parameters:
buffer- the buffer to be written.byteOffset- the start position inbufferfrom where to get bytes.byteCount- the number of bytes frombufferto write to this stream.- Throws:
IOException- if an error occurs while writing to this stream.
-
write
Description copied from class:OutputStreamWrites a single byte to this stream. Only the least significant byte of the integeroneByteis written to the stream.- Specified by:
writein classOutputStream- Parameters:
oneByte- the byte to be written.- Throws:
IOException- if an error occurs while writing to this stream.
-