Mailcap file search order:
The MailcapCommandMap looks in various places in the user's system for mailcap file entries. When requests are made to search for commands in the MailcapCommandMap, it searches mailcap files in the following order:
.mailcap in the user's home directory.
mailcap in the Java runtime.
META-INF/mailcap.
META-INF/mailcap.default
(usually found only in the activation.jar file).
(The current implementation looks for the mailcap file
in the Java runtime in the directory java.home/conf
if it exists, and otherwise in the directory
java.home/lib, where java.home is the value
of the "java.home" System property. Note that the "conf" directory was
introduced in JDK 9.)
Mailcap file format:
Mailcap files must conform to the mailcap file specification (RFC 1524, A User Agent Configuration Mechanism For Multimedia Mail Format Information). The file format consists of entries corresponding to particular MIME types. In general, the specification specifies applications for clients to use when they themselves cannot operate on the specified MIME type. The MailcapCommandMap extends this specification by using a parameter mechanism in mailcap files that allows JavaBeans(tm) components to be specified as corresponding to particular commands for a MIME type.
When a mailcap file is
parsed, the MailcapCommandMap recognizes certain parameter signatures,
specifically those parameter names that begin with x-java-.
The MailcapCommandMap uses this signature to find
command entries for inclusion into its registries.
Parameter names with the form x-java-<name>
are read by the MailcapCommandMap as identifying a command
with the name name. When the name is
content-handler the MailcapCommandMap recognizes the class
signified by this parameter as a DataContentHandler.
All other commands are handled generically regardless of command
name. The command implementation is specified by a fully qualified
class name of a JavaBean(tm) component. For example; a command for viewing
some data can be specified as: x-java-view=com.foo.ViewBean.
When the command name is fallback-entry, the value of
the command may be true or false. An
entry for a MIME type that includes a parameter of
x-java-fallback-entry=true defines fallback commands
for that MIME type that will only be used if no non-fallback entry
can be found. For example, an entry of the form text/*; ;
x-java-fallback-entry=true; x-java-view=com.sun.TextViewer
specifies a view command to be used for any text MIME type. This
view command would only be used if a non-fallback view command for
the MIME type could not be found.
MailcapCommandMap aware mailcap files have the following general form:
# Comments begin with a '#' and continue to the end of the line.
<mime type>; ; <parameter list>
# Where a parameter list consists of one or more parameters,
# where parameters look like: x-java-view=com.sun.TextViewer
# and a parameter list looks like:
text/plain; ; x-java-view=com.sun.TextViewer; x-java-edit=com.sun.TextEdit
# Note that mailcap entries that do not contain 'x-java' parameters
# and comply to RFC 1524 are simply ignored:
image/gif; /usr/dt/bin/sdtimage %s
| Modifier and Type | Field and Description |
|---|---|
| private static final String | |
| private MailcapRegistry[] | |
| private static final int |
| Access | Constructor and Description |
|---|---|
| public | |
| public | MailcapCommandMap(String
The name of the mailcap file to open fileName)Constructor that allows the caller to specify the path of a mailcap file. |
| public | MailcapCommandMap(InputStream
InputStream of the mailcap file to open is)Constructor that allows the caller to specify an InputStream containing a mailcap file. |
| Modifier and Type | Method and Description |
|---|---|
| public synchronized void | |
| private void | appendCmdsToList(Map<String, List<String>> typeHash, List<CommandInfo> cmdList)
Put the commands that are in the hash table, into the list. |
| private void | appendPrefCmdsToList(Map<String, List<String>> cmdHash, List<CommandInfo> cmdList)
Put the commands that are in the hash table, into the list. |
| private boolean | checkForVerb(List<CommandInfo> cmdList, String verb)
Check the cmdList to see if this command exists, return true if the verb is there. |
| public synchronized DataContentHandler | Returns: the DataContentHandlerthe MIME type mimeType)Implements abstract jakarta. |
| public synchronized CommandInfo[] | Returns: the CommandInfo objects representing all the commands.the MIME type mimeType)Implements abstract jakarta. |
| public synchronized CommandInfo | Returns: the CommandInfo object corresponding to the command.the MIME type mimeType, String the command name cmdName)Implements abstract jakarta. cmdName for the MIME type.
|
| private DataContentHandler | |
| private MailcapRegistryProvider | |
| public synchronized String[] | Returns: array of MIME types as stringsOverrides jakarta. |
| public synchronized String[] | Returns: array of native command entriesthe MIME type mimeType)Get the native commands for the given MIME type. |
| public synchronized CommandInfo[] | Returns: the CommandInfo objects representing the preferred commands.the MIME type mimeType)Implements abstract jakarta. |
| private void | |
| private MailcapRegistry | |
| private MailcapRegistry |
| confDir | back to summary |
|---|---|
| private static final String confDir | |
| DB | back to summary |
|---|---|
| private MailcapRegistry[] DB | |
| PROG | back to summary |
|---|---|
| private static final int PROG | |
| MailcapCommandMap | back to summary |
|---|---|
| public MailcapCommandMap() The default Constructor. | |
| MailcapCommandMap | back to summary |
|---|---|
| public MailcapCommandMap(String fileName) throws IOException Constructor that allows the caller to specify the path of a mailcap file.
| |
| MailcapCommandMap | back to summary |
|---|---|
| public MailcapCommandMap(InputStream is) Constructor that allows the caller to specify an InputStream containing a mailcap file.
| |
| addMailcap | back to summary |
|---|---|
| public synchronized void addMailcap(String mail_cap) Add entries to the registry. Programmatically added entries are searched before other entries. The string that is passed in should be in mailcap format.
| |
| appendCmdsToList | back to summary |
|---|---|
| private void appendCmdsToList(Map<String, List<String>> typeHash, List<CommandInfo> cmdList) Put the commands that are in the hash table, into the list. | |
| appendPrefCmdsToList | back to summary |
|---|---|
| private void appendPrefCmdsToList(Map<String, List<String>> cmdHash, List<CommandInfo> cmdList) Put the commands that are in the hash table, into the list. | |
| checkForVerb | back to summary |
|---|---|
| private boolean checkForVerb(List<CommandInfo> cmdList, String verb) Check the cmdList to see if this command exists, return true if the verb is there. | |
| createDataContentHandler | back to summary |
|---|---|
| public synchronized DataContentHandler createDataContentHandler(String mimeType) Implements abstract jakarta. Return the DataContentHandler for the specified MIME type.
| |
| getAllCommands | back to summary |
|---|---|
| public synchronized CommandInfo[] getAllCommands(String mimeType) Implements abstract jakarta. Get all the available commands in all mailcap files known to this instance of MailcapCommandMap for this MIME type.
| |
| getCommand | back to summary |
|---|---|
| public synchronized CommandInfo getCommand(String mimeType, String cmdName) Implements abstract jakarta. Get the command corresponding to
| |
| getDataContentHandler | back to summary |
|---|---|
| private DataContentHandler getDataContentHandler(String name) | |
| getImplementation | back to summary |
|---|---|
| private MailcapRegistryProvider getImplementation() | |
| getMimeTypes | back to summary |
|---|---|
| public synchronized String[] getMimeTypes() Overrides jakarta. Get all the MIME types known to this command map.
| |
| getNativeCommands | back to summary |
|---|---|
| public synchronized String[] getNativeCommands(String mimeType) Get the native commands for the given MIME type. Returns an array of strings where each string is an entire mailcap file entry. The application will need to parse the entry to extract the actual command as well as any attributes it needs. See RFC 1524 for details of the mailcap entry syntax. Only mailcap entries that specify a view command for the specified MIME type are returned. | |
| getPreferredCommands | back to summary |
|---|---|
| public synchronized CommandInfo[] getPreferredCommands(String mimeType) Implements abstract jakarta. Get the preferred command list for a MIME Type. The MailcapCommandMap searches the mailcap files as described above under Mailcap file search order. The result of the search is a proper subset of available commands in all mailcap files known to this instance of MailcapCommandMap. The first entry for a particular command is considered the preferred command.
| |
| loadAllResources | back to summary |
|---|---|
| private void loadAllResources(List<MailcapRegistry> v, String name) Load all of the named resource. | |
| loadFile | back to summary |
|---|---|
| private MailcapRegistry loadFile(String name) Load from the named file. | |
| loadResource | back to summary |
|---|---|
| private MailcapRegistry loadResource(String name) Load from the named resource. | |