Currently, the JAF API (MailcapCommandMap and MimetypesFileTypeMap) has been updated to support Jakarta-prefixed resources (e.g., jakarta.mailcap, jakarta.mime.types). However, to maintain backward compatibility, legacy resource files (mailcap, mime.types) also need to be loaded, with legacy files taking precedence when both forms are present.
This behavior aligns with the approach taken in Jakarta Mail 2.2.0 for provider and address map files, where both legacy (javamail.*) and Jakarta-prefixed resources are supported, but legacy entries have priority.
See jakartaee/mail-api#812
Currently, the JAF API (MailcapCommandMap and MimetypesFileTypeMap) has been updated to support Jakarta-prefixed resources (e.g., jakarta.mailcap, jakarta.mime.types). However, to maintain backward compatibility, legacy resource files (mailcap, mime.types) also need to be loaded, with legacy files taking precedence when both forms are present.
This behavior aligns with the approach taken in Jakarta Mail 2.2.0 for provider and address map files, where both legacy (javamail.*) and Jakarta-prefixed resources are supported, but legacy entries have priority.
See jakartaee/mail-api#812