[
https://issues.apache.org/jira/browse/CXF-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495467#comment-13495467
]
Daniel Kulp commented on CXF-4616:
----------------------------------
Ah. OSGi.... that certainly explains a lot. :-) Sometimes I really find
OSGi (and the differences between it an non-osgi runtimes) annoying.
Anyway, that analysis makes sense within OSGi when using some mail providers.
I'd likely want to check the servicemix specs version of the mail bundle to see
if it handles the mailcaps better. But that's just an aside.
Thanks for the extra information. Definitely helps understand the environment
that is causing the issues.
> When creating DataContentHandler, defaultCommandMap should be considered.
> -------------------------------------------------------------------------
>
> Key: CXF-4616
> URL: https://issues.apache.org/jira/browse/CXF-4616
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.6.3
> Reporter: Jinhua Wang
> Attachments: AttachmentUtil.java.patch, AttachmentUtilTest.java,
> AttachmentUtilWithoutAttachmentPartTest.java, CommandMapImpactTest.java,
> EnhancedMailcapCommandMap.java
>
>
> When creating DataContentHandler, null may be returned from CXF's static
> CommandMap. DefaultCommandMap from *CommandMap.getDefaultCommandMap()* could
> also be used to create DataContentHandler.
> Because in RI implementation,xxx.*saaj.soap.AttachmentPartImpl*,
> Some static statement would add specific content handler to default
> CommandMap.
> {code}
> CommandMap localCommandMap = CommandMap.getDefaultCommandMap();
> localMailcapCommandMap.addMailcap("text/xml" + str +
> "xxx.saaj.soap.XmlDataContentHandler");
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
