You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Benson Margulies (JIRA)" <ji...@apache.org> on 2008/08/25 04:05:44 UTC

[jira] Assigned: (CXF-1395) MtoM for text/plain causes bad XML.

     [ https://issues.apache.org/jira/browse/CXF-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benson Margulies reassigned CXF-1395:
-------------------------------------

    Assignee: Benson Margulies

> MtoM for text/plain causes bad XML.
> -----------------------------------
>
>                 Key: CXF-1395
>                 URL: https://issues.apache.org/jira/browse/CXF-1395
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>    Affects Versions: 2.1
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>
> I just added a test case to ClientMtomXopTest that exercises MtoM where the content type is text/plain rather than application/octet-stream or some other thing.
> The test, when un@Ignored, produces garbage XML that is rejected in the server's parse.
> I don't know where the problem here vis-a-vis CXF or the JAXB-RI. 
> This case is schema first The element type is base64Binary, but the code generator is for some reason declaring as String instead of DataHandler. In fact, this would be fine with me **if-it-worked**.
> Note that I have a related case working, at least client-to-server, in a code-first scenario by declaring a DataHandler and attaching the XmlMimeType annotation for text/plain.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.