This class uses buffering while reading from a BFILE. The simple constructor (the one that takes just a BFILE) uses a default buffer size that should be sufficient for most streams; however, users can specify any buffer size using an alternate constructor.
In order to to use the JAI stream objects, you will need to include the following import statements in your Java file:
import java.sql.Blob;
import oracle.sql.BFILE;
In order to use JAI with Oracle Multimedia JAI stream objects, you will also need to import classes from the oracle.ord.media.jai.io package into your Java file.
Before running the methods associated with the BfileInputStream object, the following operations must have already been performed:
import javax.media.jai.JAI;
import java.awt.image.RenderedImage;
This class uses buffering while reading from a Blob. The simple constructor (the one that takes only a Blob or a BLOB) uses a default buffer size unless an optimal buffer size can be determined by the database. Users can also specify any buffer size using an alternate constructor.
In order to to use the JAI stream objects, you will need to include the following import statements in your Java file:
import java.sql.Blob;
import oracle.sql.BFILE;
In order to use JAI with Oracle Multimedia JAI stream objects, you will also need to import classes from the oracle.ord.media.jai.io package into your Java file.
Before running the methods associated with the BlobInputStream object, the following operations must have already been performed:
import javax.media.jai.JAI;
import java.awt.image.RenderedImage;
This class uses buffering while writing to an underlying Blob. The simple constructor (the one that takes only a Blob or BLOB ) uses a default buffer size unless an optimal size can be determined by the database. Users can also specify any buffer size using an alternate constructor.
In order to to use the JAI stream objects, you will need to include the following import statements in your Java file:
import java.sql.Blob;
import oracle.sql.BFILE;
In order to use JAI with Oracle Multimedia JAI stream objects, you will also need to import classes from the oracle.ord.media.jai.io package into your Java file.
Before running the methods associated with the BlobOutputStream object, the following operations must have already been performed:
import javax.media.jai.JAI;
import java.awt.image.RenderedImage;
true.true.BlobOutputStream.flush() method to write any buffered bytes to the Blob.ByteArraySeekableOutputStream.flush() method to write any buffered bytes to the stream.FileSeekableOutputStream.flush() method to write any buffered bytes to the stream.MemoryCacheSeekableOutputStream.flush() method to write any buffered bytes to the stream.There is little need to call this method until all the data has been written because the close method includes a call to the flush method.
There is little need to call this method until all the data has been written because the close method includes a call to the flush method.
There is little need to call this method until all the data has been written because the close method includes a call to the flush method.
file.file.file.file.srcType://srcLocation/srcName.srcType://srcLocation/srcName.srcType://srcLocation/srcName.srcType://srcLocation/srcName.BfileInputStream.reset() method will return you to the last marked position in the BfileInputStream object.BlobInputStream.reset() method will return you to the last marked position in the BlobInputStream object.true.true.Users of this class should be familiar with Oracle Multimedia Reference.
Almost all methods operate on the attributes of the OrdAudio Java object in the application. The exceptions are those methods that access the audio data for read or write purposes, which are described in the following list:
file, read data from the specified file.http, read data from the resource at the specified URL.Some methods in the OrdAudio Java class are handed off to a database source plug-in or database format plug-in for processing; these methods have byte [] ctx [] as a context parameter. Applications should allocate a 64-byte array to hold any context information that may be required by a source plug-in or a format plug-in. For example, a plug-in may initialize the context information in one call and use that information in a subsequent call. The source plug-in context requires one array; the format plug-in context requires another array. For most plug-ins, 64 bytes should be sufficient. Some user-defined plug-ins may need additional space. The following example shows how to allocate a plug-in context information array:
byte [] ctx [] = new byte[1][64];
See Oracle Multimedia Reference for more information about plug-ins.
In order to run OrdAudio methods, you will need to include the following import statements in your Java file:
import oracle.ord.im.OrdMediaUtil;
import oracle.ord.im.OrdAudio;
You may also need to import classes from the following Java packages:
java.io.
java.sql.
oracle.jdbc.
Before running OrdAudio methods, the following operations must have already been performed:
For examples of making a connection and populating a local object, see Oracle Multimedia User's Guide.
Users of this class should be familiar with Oracle Multimedia Reference.
Almost all methods operate on the attributes of the OrdDoc Java object in the application. The exceptions are those methods that access the media data for read or write purposes, which are described in the following list:
file, read data from the specified file.http, read data from the resource at the specified URL.Some methods in the OrdAudio Java class are handed off to a database source plug-in or database format plug-in for processing; these methods have byte [] ctx [] as a context parameter. Applications should allocate a 64-byte array to hold any context information that may be required by a source plug-in or a format plug-in. For example, a plug-in may initialize the context information in one call and use that information in a subsequent call. The source plug-in context requires one array; the format plug-in context requires another array. For most plug-ins, 64 bytes should be sufficient. Some user-defined plug-ins may need additional space. The following example illustrates how to allocate a plug-in context information array:
byte [] ctx [] = new byte[1][64];
See Oracle Multimedia Reference for more information about plug-ins.
In order to run OrdDoc methods, you will need to include the following import statements in your Java file:
import oracle.ord.im.OrdMediaUtil;
import oracle.ord.im.OrdDoc;
You may also need to import classes from the following Java packages:
java.io.
java.sql.
oracle.jdbc.
Before running OrdDoc methods, the following operations must have already been performed:
For examples of making a connection and populating a local object, see Oracle Multimedia User's Guide.
Users of this class should be familiar with Oracle Multimedia Reference.
Almost all methods operate on the attributes of the OrdImage Java object in the application. The exceptions are those methods that access the image data for read or write purposes, which are described in the following list:
file, read data from the specified file.http, read data from the resource at the specified URL.Some methods in the OrdImage Java class are handed off to a database source plug-in for processing; these methods have byte [] ctx [] as a context parameter. Applications should allocate a 64-byte array to hold any context information that may be required by a source plug-in. For example, a plug-in may initialize the context information in one call and use that information in a subsequent call. For most plug-ins, 64 bytes should be sufficient. Some user-defined plug-ins may need additional space. The following example shows how to allocate a plug-in context information array:
byte [] ctx [] = new byte[1][64];
See Oracle Multimedia Reference for more information about plug-ins.
In order to run OrdImage methods, you will need to include the following import statements in your Java file:
import oracle.ord.im.OrdMediaUtil;
import oracle.ord.im.OrdImage;
You may also need to import classes from the following Java packages:
java.io.
java.sql.
oracle.jdbc.
Before running OrdImage methods, the following operations must have already been performed:
For examples of making a connection and populating a local object, see Oracle Multimedia User's Guide.
Users of this class should be familiar with Oracle Multimedia Reference.
Before running OrdMediaUtil methods, the following operations must have already been performed:
For examples of making a connection and populating a local object, see Oracle Multimedia User's Guide.
Users of this class should be familiar with Oracle Multimedia Reference.
Almost all methods operate on the attributes of the OrdVideo Java object in the application. The exceptions are those methods that access the video data for read or write purposes, which are described in the following list:
file, read data from the specified file.http, read data from the resource at the specified URL.Some methods in the OrdVideo Java class are handed off to a database source plug-in or database format plug-in for processing; these methods have byte [] ctx [] as a context parameter. Applications should allocate a 64-byte array to hold any context information that may be required by a source plug-in or a format plug-in. For example, a plug-in may initialize the context information in one call and use that information in a subsequent call. The source plug-in context requires one array; the format plug-in context requires another array. For most plug-ins, 64 bytes should be sufficient. Some user-defined plug-ins may need additional space. The following example shows how to allocate a plug-in context information array:
byte [] ctx [] = new byte[1][64];
See Oracle Multimedia Reference for more information about plug-ins.
In order to run OrdVideo methods, you will need to include the following import statements in your Java file:
import oracle.ord.im.OrdMediaUtil;
import oracle.ord.im.OrdVideo;
You may also need to import classes from the following Java packages:
java.io.
java.sql.
oracle.jdbc.
Before running OrdVideo methods, the following operations must have already been performed:
For examples of making a connection and populating a local object, see Oracle Multimedia User's Guide.
The offset may be set beyond the end of the stream. Setting the offset beyond the end of the stream does not change the stream length; the stream length will change only by writing after the offset has been set beyond the end of the stream.
The offset may be set beyond the end of the stream. Setting the offset beyond the end of the stream does not change the stream length; the stream length will change only by writing after the offset has been set beyond the end of the stream.
In Java, a byte array cannot be longer than 2 gigabytes, therefore the value of the pos parameter cannot be larger than 2^31-1.
The offset may be set beyond the end of the stream. Setting the offset beyond the end of the stream does not change the stream length; the stream length will change only by writing after the offset has been set beyond the end of the stream.
The offset may be set beyond the end of the stream. Setting the offset beyond the end of the stream does not change the stream length; the stream length will change only by writing after the offset has been set beyond the end of the stream.
The offset may be set beyond the end of the stream. Setting the offset beyond the end of the stream does not change the stream length; the stream length will change only by writing after the offset has been set beyond the end of the stream.
In order to use JAI with Oracle Multimedia JAI stream objects, you will need to import classes from the oracle.ord.media.jai.io package into your Java file.
All methods except the close method will throw an IOException error if they are called on a stream that is already closed. Calling the close method on a stream that is already closed will have no effect.
This method may skip over some smaller number of bytes, possibly zero. This action may result from a number of conditions. For example, reaching the end of the stream before the specified number of bytes have been skipped. This method never throws an end-of-file exception.
The number of bytes skipped may be smaller than the specified number; for example, the number would be smaller if the end of the file is reached.
The number of bytes skipped may be smaller than the specified number; for example, the number would be smaller if the end of the file is reached.
This method may skip over some smaller number of bytes, possibly zero. This action may result from a number of conditions. For example, reaching the end of the stream before the specified number of bytes have been skipped. This method never throws an end-of-file exception.
See the MemoryCacheSeekableOutputStream class for information about restrictions and implementation details for the class.