[jira] Updated: (WSCOMMONS-542) OMText doesn't get serialized as a separate mime part (optimized XOP/MTOM) in some cases

["Lari Hotari (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WSCOMMONS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lari Hotari updated WSCOMMONS-542:
----------------------------------

    Summary: OMText doesn't get serialized as  a separate mime part (optimized XOP/MTOM) in some cases  (was: OMText doesn't get serialized as  a separate mime part (optimized) in XOP/MTOM in some cases)

> OMText doesn't get serialized as  a separate mime part (optimized XOP/MTOM) in some cases
> -----------------------------------------------------------------------------------------
>
>                 Key: WSCOMMONS-542
>                 URL: https://issues.apache.org/jira/browse/WSCOMMONS-542
>             Project: WS-Commons
>          Issue Type: Bug
>          Components: AXIOM
>    Affects Versions: Axiom 1.2.8
>            Reporter: Lari Hotari
>
> We are using Spring Webservices 1.5.8 + Axiom 1.2.8 . 
> We had a problem in getting Axiom to output optimized attachments.
> The SOAP message "template" is first created with separate logic in Spring Webservices using a Transformer (WebServiceTemplate.sendSourceAndReceiveToResult).
> The Axiom dom is then manipulated in Spring WS's WebServiceMessageCallback to add the file attachment.
> This is the recommended way to do XOP/MTOM attachments is Spring WS.
> Here's the only difference between the working and un-working versions:
> this optimizes the added OMText element:
> (body is instance of org.apache.axiom.soap.SOAPBody)
> {code}
> body.getFirstElement().getFirstChildWithName(null).addChild(omtext);
> {code}
> this doesn't optimize the added OMText element:
> {code}
> body.getFirstElement().getFirstElement().addChild(omtext);
> {code}
> And this version works too:
> {code}
> body.getFirstElement().getFirstChildWithName(null);
> body.getFirstElement().getFirstElement().addChild(omtext);
> {code}
> This might be some kind of similar "touched"/"untouched" related bug as WSCOMMONS-324.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.