Details
-
Type:
Bug
-
Status: Closed
-
Priority:
P4
-
Resolution: Fixed
-
Affects Version/s: 1.1.2, 1.3.0
-
Fix Version/s: 1.0.2
-
Component/s: other-libs
-
Labels:
-
Subcomponent:
-
Resolved In Build:1.0.2
-
CPU:generic
-
OS:generic
-
Verification:Not verified
Description
Name: skT45625 Date: 08/31/2000
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)
When JAF 1.0.1 is installed as an extension (activation.jar in jre/lib/ext), its
MimeTypesFileTypeMap and MailcapCommandMap classes no longer look at
META-INF/mime.types and META-INF/mailcap, as documented.
Instead, the META-INF/mimetypes.default and META-INF/mailcap.default entries
from activation.jar take precedence.
This was reported previously as bug 4263185 as a problem affecting both JavaMail
and JAF. That bug was closed when solved for JavaMail, but the problem remains
with JAF.
(Review ID: 109169)
======================================================================
Attachments
Issue Links
- duplicates
-
JDK-4483204 JAF: doesn't support extdirs class loader
-
- Closed
-