diff -r ac3f5a39d4ff -r b2f720a258c4 jaxws/src/java.activation/share/classes/javax/activation/MailcapCommandMap.java --- a/jaxws/src/java.activation/share/classes/javax/activation/MailcapCommandMap.java Wed Jul 05 20:29:22 2017 +0200 +++ b/jaxws/src/java.activation/share/classes/javax/activation/MailcapCommandMap.java Wed Apr 22 15:26:20 2015 +0400 @@ -45,14 +45,13 @@ * 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.
- * /lib/mailcap
.
- * META-INF/mailcap
.
- * META-INF/mailcap.default
- * (usually found only in the activation.jar
file).
+ * * Mailcap file format:
@@ -70,46 +69,43 @@
*
* When a mailcap file is
* parsed, the MailcapCommandMap recognizes certain parameter signatures,
- * specifically those parameter names that begin with
+ * some data can be specified as: {@code x-java-view=com.foo.ViewBean}.
*
- * When the command name is
*
* MailcapCommandMap aware mailcap files have the
- * following general form:
- *
+ * # 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
+ * }
*
* @author Bart Calder
* @author Bill Shannon
@@ -451,7 +447,7 @@
}
/**
- * Get the command corresponding to x-java-
.
+ * specifically those parameter names that begin with {@code x-java-}.
* The MailcapCommandMap uses this signature to find
* command entries for inclusion into its registries.
- * Parameter names with the form x-java-<name>
+ * Parameter names with the form {@code x-java-
- * content-handler
the MailcapCommandMap recognizes the class
+ * with the name name. When the name is {@code
+ * 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
.fallback-entry
, the value of
- * the command may be true
or false
. An
+ * When the command name is {@code fallback-entry}, the value of
+ * the command may be {@code true} or {@code false}. An
* entry for a MIME type that includes a parameter of
- * x-java-fallback-entry=true
defines fallback commands
+ * {@code 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
+ * can be found. For example, an entry of the form {@code 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.
- * # 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:
+ * following general form:
+ * {@code
+ * # Comments begin with a '#' and continue to the end of the line.
+ *
- * # 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
- *
- * cmdName
for the MIME type.
+ * Get the command corresponding to {@code cmdName} for the MIME type.
*
* @param mimeType the MIME type
* @param cmdName the command name