[
https://issues.apache.org/jira/browse/CXF-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464346
]
Dan Diephouse commented on CXF-284:
-----------------------------------
I think we need to take a closer look at SwA. There are basically two ways to
do it
1. SwA WS-I profile
2. legacy way - like Axis 1.x
I don't know of one soap stack that supports the SwA Profile that doesn't also
support MTOM, so supporting that is kind of worthless. What we really want is
to figure out a way to support case #2. I've written a little more about this
issue here:
http://netzooid.com/blog/2007/01/04/the-ws-i-attachmentsprofile-is-a-sham/
I also asked around on the JAXB list on how to support case #2, but they didn't
know of a way with JAXB. I might see if I can wire something up using the XFire
Aegis databinding library.
> Support SOAP with Attachments in Runtime
> ----------------------------------------
>
> Key: CXF-284
> URL: https://issues.apache.org/jira/browse/CXF-284
> Project: CXF
> Issue Type: New Feature
> Affects Versions: 2.0-M1
> Reporter: Dan Diephouse
> Fix For: 2.0-RC
>
>
> We should look at supporting SOAP with attachments correctly in the runtime.
> I think the deserialization probably works correctly, but the
> AttachmentSerializer I wrote probably needs improvements. Specifically:
> 1. we should need to be able to write non application/xop+xml content types
> 2. We need to support writing 8bit Content-Transfer-Encodings (I think...)
> 3. We need to support Base64 encoding (and decoding?) of the attachments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
