Overview  Package   Class  Use  Deprecated  Index
Home >> All >> java >> [ nio overview ]	PREV CLASS  NEXT CLASS
SUMMARY:  JAVADOC |  SOURCE |  DOWNLOAD | NESTED | FIELD | CONSTR | METHOD	DETAIL: FIELD | CONSTR | METHOD

---

java.nio
Class MappedByteBuffer  

java.lang.Object
  java.nio.Buffer
      java.nio.ByteBuffer
          java.nio.MappedByteBuffer

All Implemented Interfaces:

java.lang.Comparable

Direct Known Subclasses:

MappedByteBufferImpl

---

public abstract class MappedByteBuffer

extends ByteBuffer

Since:

1.4

---

Field Summary

 

Fields inherited from class java.nio.ByteBuffer

array_offset, backing_buffer, endian

 

Fields inherited from class java.nio.Buffer

address, cap, limit, mark, pos

 

Constructor Summary
(package private)	MappedByteBuffer(int capacity, int limit, int position, int mark)

 

Method Summary
protected  void	finalize()           Called on an object by the Virtual Machine at most once, at some point after the Object is determined unreachable but before it is destroyed.
MappedByteBuffer	force()
(package private)  void	forceImpl()
boolean	isLoaded()
(package private)  boolean	isLoadedImpl()
MappedByteBuffer	load()
(package private)  void	loadImpl()
(package private)  void	unmapImpl()

 

Methods inherited from class java.nio.ByteBuffer

allocate, allocateDirect, array, arrayOffset, asCharBuffer, asDoubleBuffer, asFloatBuffer, asIntBuffer, asLongBuffer, asReadOnlyBuffer, asShortBuffer, compact, compareTo, duplicate, equals, get, get, get, get, getChar, getChar, getDouble, getDouble, getFloat, getFloat, getInt, getInt, getLong, getLong, getShort, getShort, hasArray, hashCode, isDirect, order, order, put, put, put, put, put, putChar, putChar, putDouble, putDouble, putFloat, putFloat, putInt, putInt, putLong, putLong, putShort, putShort, shiftDown, slice, toString, wrap, wrap

 

Methods inherited from class java.nio.Buffer

capacity, checkArraySize, checkForOverflow, checkForOverflow, checkForUnderflow, checkForUnderflow, checkIfReadOnly, checkIndex, clear, flip, hasRemaining, isReadOnly, limit, limit, mark, position, position, remaining, reset, rewind

 

Methods inherited from class java.lang.Object

clone, getClass, notify, notifyAll, wait, wait, wait

 

Constructor Detail

MappedByteBuffer

MappedByteBuffer(int capacity,
                 int limit,
                 int position,
                 int mark)

Method Detail

forceImpl

void forceImpl()

---

force

public final MappedByteBuffer force()

---

isLoadedImpl

boolean isLoadedImpl()

---

isLoaded

public final boolean isLoaded()

---

loadImpl

void loadImpl()

---

load

public final MappedByteBuffer load()

---

unmapImpl

void unmapImpl()

---

finalize

protected void finalize()
                 throws java.lang.Throwable

Description copied from class: java.lang.Object

Called on an object by the Virtual Machine at most once, at some point after the Object is determined unreachable but before it is destroyed. You would think that this means it eventually is called on every Object, but this is not necessarily the case. If execution terminates abnormally, garbage collection does not always happen. Thus you cannot rely on this method to always work. For finer control over garbage collection, use references from the java.lang.ref package.

Virtual Machines are free to not call this method if they can determine that it does nothing important; for example, if your class extends Object and overrides finalize to do simply super.finalize().

finalize() will be called by a java.lang.Thread that has no locks on any Objects, and may be called concurrently. There are no guarantees on the order in which multiple objects are finalized. This means that finalize() is usually unsuited for performing actions that must be thread-safe, and that your implementation must be use defensive programming if it is to always work.

If an Exception is thrown from finalize() during garbage collection, it will be patently ignored and the Object will still be destroyed.

It is allowed, although not typical, for user code to call finalize() directly. User invocation does not affect whether automatic invocation will occur. It is also permitted, although not recommended, for a finalize() method to "revive" an object by making it reachable from normal code again.

Unlike constructors, finalize() does not get called for an object's superclass unless the implementation specifically calls super.finalize().

The default implementation does nothing.

---

Overview  Package   Class  Use  Deprecated  Index
Home >> All >> java >> [ nio overview ]	PREV CLASS  NEXT CLASS
SUMMARY:  JAVADOC |  SOURCE |  DOWNLOAD | NESTED | FIELD | CONSTR | METHOD	DETAIL: FIELD | CONSTR | METHOD

---