JDK-8043129 : JAF initialisation in SAAJ clashing with the one in javax.mail
  • Type: Bug
  • Component: xml
  • Sub-Component: jax-ws
  • Affected Version: 7u55
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2014-05-14
  • Updated: 2016-08-26
  • Resolved: 2014-05-23
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availabitlity Release.

To download the current JDK release, click here.
JDK 7 JDK 8 JDK 9
7u76Fixed 8u20Fixed 9 b15Fixed
Related Reports
Duplicate :  
Description
After initialisation of SAAJ components the JAF handlers defined defined by javax.mail don't work.
Attached testcase, containing workaround - after SAAJ initialisation, re-initialise javax.mail handler:
-------------------
MailcapCommandMap mailMap = (MailcapCommandMap) CommandMap.getDefaultCommandMap();
mailMap.addMailcap("multipart/mixed;;x-java-content-handler=com.sun.mail.handlers.multipart_mixed");

Comments
The nighlty results for the binaries with the fix doesn't have any issues related to JDK-8043129. Please, provide a justification why we need this fix in CPU14_03 so late. Has it been requested by any customers? Why we can't move it in BPR?
2014-06-11

Please, push the fix in 8u-CPU repo in oder to perfrom nightly testing.
2014-06-04