[
https://issues.apache.org/jira/browse/CXF-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630843#action_12630843
]
Benson Margulies commented on CXF-1395:
---------------------------------------
This is just the JAXB failure to allow MTOM from a plain String as opposed to a
DataHandler or such. It is confused by asserting in a place where CXF can't
cope cleanly with it.
> 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 [EMAIL PROTECTED], 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.
