cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jara Cesnek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-1352) SOAP with Attachments is not working or cannot get to work !?
Date Fri, 04 Jan 2008 08:14:34 GMT

    [ https://issues.apache.org/jira/browse/CXF-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555847#action_12555847
] 

Jara Cesnek commented on CXF-1352:
----------------------------------

We migrate from Xfire to CXF expected SwA will work. SwA was the main reason to migrate.

We have java server and Delphi clients. This is the WS stack supporting SwA and do not support
MTOM you looking for.




> 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.


Mime
View raw message