[
https://issues.apache.org/jira/browse/CXF-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Mazza closed CXF-1352.
---------------------------
Resolution: Duplicate
Duplicate with CXF-284
> SOAP with Attachments is not working or cannot get to work !?
> -------------------------------------------------------------
>
> Key: CXF-1352
> URL: https://issues.apache.org/jira/browse/CXF-1352
> Project: CXF
> Issue Type: Bug
> Components: Aegis Databinding, Configuration, Documentation, Samples
> Affects Versions: 2.0.3
> Reporter: Jara Cesnek
>
> SOAP with Attachments generate always xsd:base64Binary into WSDL.
> Even after hours trying I cannot get expected stuff in WSDL like this :
> <mime:multipartRelated>
> <mime:part>
> <soap:body parts="" namespace="http://attachment.tip/";
> use="literal"/>
> </mime:part>
> <mime:part>
> <mime:content part="octet" type="application/octet-stream"/>
> </mime:part>
> </mime:multipartRelated>
>
> 1) No documentation on CXF web site at all (so may be I am totaly wrong about
> switching on SwA in CXF ?!)
> 2) In apache-cxf-2.0.3-incubator-src.zip is one test case
> ClientServerSwaTest. Cant compile because missing SwAServiceInterface.java
> and other.
> Anyway I follow test case and publish this method :
> @WebMethod
> public void testDataHandler(DataHandler arg1) {
> }
> In wsdl arg1 appears as xsd:base64Binary (same result as arg1 type was
> byte[]).
> Clients sends data in base64 format and arg1 in this method is always NULL !
> This seems to me as bug.
> 1) Should I explicitly switch on SwA support ?
> 2) Should use @SOAPBinding(style=SOAPBinding.Style.RPC)
> 3) Should @XmlMimeType("application/octet-stream")
> 4) Support this AegisDataBinding ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
