| java.lang.Object | |
| ↳ | android.content.res.AssetManager |
Provides access to an application's raw asset files; see Resources
for the way most applications will want to retrieve their resource data.
This class presents a lower-level API that allows you to open and read raw
files that have been bundled with the application as a simple stream of
bytes.
| Nested Classes | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| AssetManager.AssetInputStream | |||||||||||
| Constants | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| int | ACCESS_BUFFER | Mode for open(String, int): Attempt to load contents into
memory, for fast small reads. |
|||||||||
| int | ACCESS_RANDOM | Mode for open(String, int): Read chunks, and seek forward and
backward. |
|||||||||
| int | ACCESS_STREAMING | Mode for open(String, int): Read sequentially, with an
occasional forward seek. |
|||||||||
| int | ACCESS_UNKNOWN | Mode for open(String, int): no specific information about how
data will be accessed. |
|||||||||
| Public Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Close this asset manager.
| |||||||||||
Get the locales that this asset manager contains data for.
| |||||||||||
Return a String array of all the assets at the given path.
| |||||||||||
Open an asset using ACCESS_STREAMING mode.
| |||||||||||
Open an asset using an explicit access mode, returning an InputStream to
read its contents.
| |||||||||||
Retrieve a parser for a compiled XML file.
| |||||||||||
Retrieve a parser for a compiled XML file.
| |||||||||||
| Protected Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Invoked when the garbage collector has detected that this instance is no longer reachable.
| |||||||||||
|
[Expand]
Inherited Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
From class
java.lang.Object
| |||||||||||
Mode for open(String, int): Attempt to load contents into
memory, for fast small reads.
Mode for open(String, int): Read chunks, and seek forward and
backward.
Mode for open(String, int): Read sequentially, with an
occasional forward seek.
Mode for open(String, int): no specific information about how
data will be accessed.
Get the locales that this asset manager contains data for.
Return a String array of all the assets at the given path.
| path | A relative path within the assets, i.e., "docs/home.html". |
|---|
| IOException |
|---|
Open an asset using ACCESS_STREAMING mode. This provides access to files that have been bundled with an application as assets -- that is, files placed in to the "assets" directory.
| fileName | The name of the asset to open. This name can be hierarchical. |
|---|
| IOException |
|---|
Open an asset using an explicit access mode, returning an InputStream to read its contents. This provides access to files that have been bundled with an application as assets -- that is, files placed in to the "assets" directory.
| fileName | The name of the asset to open. This name can be hierarchical. |
|---|---|
| accessMode | Desired access mode for retrieving the data. |
| IOException |
|---|
| IOException |
|---|
| IOException |
|---|
Retrieve a parser for a compiled XML file.
| fileName | The name of the file to retrieve. |
|---|
| IOException |
|---|
Retrieve a parser for a compiled XML file.
| cookie | Identifier of the package to be opened. |
|---|---|
| fileName | The name of the file to retrieve. |
| IOException |
|---|
Invoked 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 finalize are 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 explicit close method (and implement
Closeable), and insist that callers manually dispose of instances. This
works well for something like files, but less well for something like a BigInteger
where 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
ReferenceQueue and 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.
| Throwable |
|---|