MTOM attachments are not output by the jsr181 component
-------------------------------------------------------

                 Key: SM-598
                 URL: https://issues.apache.org/activemq/browse/SM-598
             Project: ServiceMix
          Issue Type: Bug
          Components: servicemix-jsr181
    Affects Versions: 3.0
            Reporter: Hari Iyer


While sending an MTOM attachment to the component works, retrieving an 
attachment does not:
Operation: DataSource getDocumentById(String documentId)
The request that gets created is: 

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><soap:Body><GetDocumentById
 
xmlns="http://webservices.sterling.com";><in0>abcd</in0></GetDocumentById></soap:Body></soap:Envelope>
 
------=_Part_0_12577309.1158352665757-- 

The response that comes back is: 
<?xml version='1.0' encoding='UTF-8'?><soap:Envelope 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><GetDocumentByIdResponse
 xmlns="http://webservices.sterling.com";><out 
xmlns:ns1="http://www.w3.org/2004/11/xmlmime"; ns1:mimeType="text"><Include 
xmlns="http://www.w3.org/2004/08/xop/include"; 
href="cid:11583526659604-182379438@http://www.w3.org/2001/XMLSchema"; 
/></out></GetDocumentByIdResponse></soap:Body></soap:Envelope> 

The client gives the error: 
org.codehaus.xfire.fault.XFireFault: Could not find the attachment 
cid:11583526659604-182379438@http://www.w3.org/2001/XMLSchema 
        at 
org.codehaus.xfire.aegis.type.mtom.AbstractXOPType.readInclude(AbstractXOPType.java:62)
 

The attachment is missing from the response. This same request works correctly 
in a pure XFire deployment. 


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to