Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A0BE7D3F0 for ; Mon, 12 Nov 2012 18:17:13 +0000 (UTC) Received: (qmail 7601 invoked by uid 500); 12 Nov 2012 18:17:13 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 7522 invoked by uid 500); 12 Nov 2012 18:17:13 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 7111 invoked by uid 99); 12 Nov 2012 18:17:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Nov 2012 18:17:12 +0000 Date: Mon, 12 Nov 2012 18:17:12 +0000 (UTC) From: "Daniel Kulp (JIRA)" To: issues@cxf.apache.org Message-ID: <1495765478.101633.1352744232960.JavaMail.jiratomcat@arcas> In-Reply-To: <1055554121.73245.1352188692229.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (CXF-4616) When creating DataContentHandler, defaultCommandMap should be considered. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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